A former community discussing the business of software, from the smallest shareware operation to Microsoft. A part of Joel on Software.
We're closed, folks!
Doug Nebeker ("Doug")
We have decided to implement unit testing on our new project that we will begin shortly. If it is done properly it can be very useful. But I am concerned that if we don't approach it the right way it can end up being a waste of time and something that makes the team hate the work.
So we want an expert or do some training courses. We need to prepare ourselves for the challenges ahead as nobody on the team has any real experience doing this. Does anybody have any advice in making the transition from a standard development approach to TDD?
It is not clear exactly what you are planning to do. Is it "unit testing" where you add some tests to the most important classes/modules? Or is it full TDD where the programmer will write a few lines of code and then immediately write 2x or 3x that number of lines in tests and then repeat the cycle?
"Or is it full TDD where the programmer will write a few lines of code and then immediately write 2x or 3x that number of lines in tests"
That's not what TDD is. You write unit tests first, they fail, then write the code so they pass. Rinse and repeat. It forces you to create the code that everyone thinks it will be (the tests).
UI testing is going to be the tricky part.
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz