Explore >> Select a destination
|
You are here 
|
jimpurbrick.com | ||
| | | | |
everythingfunctional.wordpress.com
|
|
| | | | | The answer to the question of whether we should write automated test suites has largely been settled. We absolutely should write unit tests, and possibly even integration and end-to-end tests. But as acceptance of this practice grew, and adoption became more widespread, a follow-up question arose; How many tests should we write? How do we... | |
| | | | |
team-agile.com
|
|
| | | | | Early on when trying to apply Agile methods to software development I found a lot of the challenges were in the area of software testing. Not just because a lot more automated testing was being done, but because requirements would shift and change rapidly. Many levels of rapid feedback needed to be in place to | |
| | | | |
www.softdevtube.com
|
|
| | | | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | |
| | | | |
www.byjp.me
|
|
| | | github.com Ruby-DLC is now available on github, and consequently as a gem! You can install with1: gem sources -a https://gems.github.com sudo gem install jphastings-dlc There's a gist explaining how to use the library and the rdoc documentation is still available on my project page. Please file an issue if you have any problems with the code, I haven't checked it thoroughly! Import note: This syntax is incorrect today, and the code only supports Ruby 1.x, so you'll have to make your own way if you're interested in using this!?? | ||
