Had a great time today at NDC London presenting my session “Testing Economics”. Now to enjoy the rest of it. Here are the slides. You can catch the video here. The session is how TDD and other day to day testing activities impact our development time, value and costs. Testing economics101 from Gil Zilberfeld
The post, one in a series of how to make code easierf or unit testing, and somewhat overloaded, now appears on the Everyday Unit Testing site. Check it out!
The post, one of a series on making code testable for unit testing is somewhat classy. now appears on the Everyday Unit Testing site. Check it out!
The next post in the “Legacy Code to Testable Code”, somewhat wanting more, is now on the Everyday Unit Testing site. Check it out!
The new post, in the “Legacy Code to Tetable Code” on unit testing is somewhat accessible, now on the Everyday Unit Testing site. Check it out!
This post, somewhat painfully, now appears on the Everyday Unit Testing site. It’s about making legacy code easier for unit testing by refactoring the code by method extraction. Check it out!
This post, namely, now appears on Everyday Unit Testing. It’s about refactoring legacy code for unit testing by renaming methods and variables. Check it out!
This post, comparable or not, now appears in the Everyday Unit Testing site. It’s on the idea that TDD equals good design, while it’s really not, and it probably still needs refactoring to get it to be good. Check it out! Image source: https://www.flickr.com/photos/microassist/7268711202/
This post, moved to Everyday Unit Testing for economic reasons. Check it out! Image source: http://marketingbones.com/understanding-economics/
The ISO 29119 is making waves in the testing communities, regarding its content and necessity. Its focus on test planning and documentation gets modern testers to ask why. I’ve worked in an ISO certified company, so maybe I can shed light from my past experience. ISO standards are written by committees, which are made of