Linked by Eugenia Loli-Queru on Sun 2nd Oct 2005 20:30 UTC
The Scrum methodology can pose a challenge for software testers who are used to more traditional waterfall-inspired development processes. Jonathan Kohl relates his experiences working on Scrum teams who found some clear advantages in changing their methods.
Thread beginning with comment 39360
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Unit tests written before code
by rayiner on Mon 3rd Oct 2005 03:17
in reply to "Unit tests written before code"
Member since:2005-07-06
I can't generally do this either, and I'm not a particular big fan of the practice. Designing the interface before at least prototyping the code always seems to lead me to baroque, inelegant interfaces. I prefer to start with a basic kernel that does the essential job of what a particular component needs to do, then use the knowledge gained from that exercise to design an interface that fits both the client of the component, as well as the implementation of that component.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
I've never been able to do this well. It feels more natural to develop the first iteration of my unit of code, then create the unit test. The unit test will invariably drive the remaining development iterations of the module that I'm building. The unit test will evolve with each iteration as well.
Am I missing something? Maybe I just stuck in my ways.