TesterAndTheDeveloper * Guard the programmer's rights

* Help the programmers design more testable code

* Help defining Unit tests (does the system work correctly); (???)- maybe not defining but giving examples to base tests on (jcg) (I think the tester can pair with developer for some unit testing, perhaps to enhance testing expertise, but unit testing is really a design activity - lc)

* "Questioning" maybe "Investigation" is a better word

* Bring a customer's perspective during coding

* Pair testing; working with developer to test the story

* Gives feedback to the developers on bugs found, and discusses whether some of the bugs might be covered by a unit test. For instance: if the developer only defines test cases based on equivalence partitioning, where boundary value analysis might be more appropriate.

Back to AgileTesting