I'm fairly new so please bear with me. I'm looking for thoughts, suggestions, ideas, anything regarding TDD and QA's participation.
I work for a small company and they are leaning towards using Test Driven Development (or parts of it). My question is how QA will fit into this? From the articles I've read, it sounds like TDD is a design technique, not a testing technique and that programmers create the unit tests. However, my manager is thinking of having QA develop the unit tests, which the programmers would then code. It does not sound like TDD to me, but is this a good idea?
Anyone here have any experience or insight into this? Not necessarily about who creates the unit test, but how it all gels?
First of all term QA donít fit for person creating unit tests (please search description).
In my company testers (not QA) sometimes write unit tests to complete unit test suite created by developers, but never Ė to drive development. I believe if tester decide (actually design) interfaces then he is actually architect and if you have architect role without architect training/experience you are going to fail.
I would suggest that what you call QA are role doing review of unit tests and their coverage, submitting defects and suggestions against unit test suite (not the product itself).