Timeline for What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2012 at 0:59 | comment | added | Aruna | I partially agree with that. After the test cases are moved to BAT the ownership does change. But before that, the new feature test cases author should be accountable for handover of a robust high quality suite to the BAT team. For the future releases the BAT team could be held accountable | |
| Mar 4, 2012 at 6:33 | comment | added | Aniket | True, while testers might move between projects, IMO, so should ownership. If the existing tester moves, a new one should be handed ownership of their TCs. | |
| Mar 4, 2012 at 2:52 | comment | added | Aruna | +1 These are very important points. Typically ownership of failures is a challenge because the resource who automated the new feature test cases might have moved to a different project when we are planning to move his test cases to BAT. The communication plan for failures, ownership and maintaining a high test code qualtiy are great points and deserves very high marks from me! | |
| Mar 2, 2012 at 17:50 | history | answered | Aniket | CC BY-SA 3.0 |