Originally posted by David Peterson:
I'm not 100% sure about your question. [...]?
Originally posted by Michal Harezlak:
JUnit as a technology and what it means for a QA guy (have them involved since start
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Ilja Preuss:
Well, I am also not sure what you are getting at, but here seems to be a misunderstanding. JUnit is *mainly* a tool for the developers, not for the QA guys.
It's still a good idea to involve them early, though. In Extreme Programming, for example, you would want to have them help the Customer come up with Acceptance Tests using tools such as FitNesse.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |