Developers Reviewing test cases.

Recently I came across one process. Reviewing of test cases by developers. In my team testers are writing test cases (or scenarios) and getting reviewed them by developers, and the net result is developers who are finding test cases are 'suddenly' seeing new conditions, and remembering that they missed these conditions in their unit test or code. Hence, in my company code freeze date is about to change and net result is almost our test cases are passing , without much Bug filing.

Is this good practice? I definitely don't think so. Either the code freeze date should be rigid or Test case review shouldn't be done by developers. It should either inside test team or if it is needed product management should take care of this.

1 opinions:

Giri said...

I had sent Test Cases to developers for their review in Agile sprints. This is make sure the my understanding on the User story for which the test cases written are correct and we are in the same page. This is very much needed when there is not much time to understand the requirements, especially in Agile.

But still I not sure that all developers will change their code after reviewing the test cases. In your case, then the developers are not good enough to understand the requirement or must have failed in their validation.