When asked:”What’s the best thing I can do right now to improve my code quality” I always answer: code reviews. A code review is the best bug preventer out there. And even more, I like its older brother better: Pair programming. Because if a code review finds bugs after the fact, working in pairs finds
A few weeks ago, I got a chance to talk with Lisa Crispin. Lisa is a prominent figure in the testing world, and co-authored “Agile Testing”. This was a great opportunity for me to talk to someone from the tester side, as usually I talk with developers. And I felt this was more of a
Last week I had great time hosting a Typemock Webinar called “10 secret unit testing tips”. The fun thing was that I’ve discovered both in preparation and answering questions live that I have at least 20 tips in me for at least two more webinars. So prepare for “10 secret unit testing tips strike back”
At NDC I was fortunate to take part in a session of Cyber Dojo, run by Jon Jagger and Olve Maudal. You can have a taste at it online, but it’s better experienced with a guide. The attendees pair up, select a kata and a programming language and start adding features and tests. Every 5
I’m a fan of “House”. I’m currently catching up on the 7th season, where the theme is about truth and lies. For those leaving in a cave with no cable TV, “House” is about a brilliant, misanthropic doctor who runs a diagnostic team in a hospital. In each episode the team dives into a mystery
This is the presentation I gave today at the “QA and Development in Agile” conference (It’s a bit more detailed than what the people in the room saw). This wasn’t a technical presentation, just an overview to the newly initiated to unit testing – third of the room wrote unit tests, the rest didn’t. And
As part of my ADC experience, I enjoyed being part of Gojko Adzic’s session: The Specification Game. The room was divided to groups of four – there were 6 teams. Each group included a product owner, developers and testers. Gojko and his team were the customers. They rolled out a product they needed: a Black
One of the sessions at ADC2011 that I understood (even though it was in German), was Bjorn Rochel’s talk on test organization. Bjorn told a story of the evolution of his experience writing tests, and how to organize them. For example, he started out with a test class, called CalculatorTests, and every method name ended
ADC2011 is over, and I had a mighty fun time. Like I open my talks, I’d like to speak first on my favorite subject: me. I had two talks, one on unit testing SharePoint applications, and the other about tools for identifying issues in multithreaded apps (slides below). I can tell you that all those
Something strange is going through TDD land these last couple of weeks. First it was Uncle Bob,with a new TDD theory – making tests pass in a certain order, actually helps incremental design, leading to a better solution. This is a very interesting post, and if he’s right, he might have discovered the cornerstone of