Question:

Test Management. I've read most of the help about how to approach testing and test management within VersionOne. Under the topic "Test Planning". What I'm not clear on is what the process/flow is within this product. A 'traditional' requirements tracking product would move a tracker item from a developer to a tester by changing the current owner or state. How does a tester know to test something? Should the developer set the state of a backlog item to 'Done'? Should the developer assign the backlog item (or task) to a tester as the owner? With regards to tests, is there a way to view all the tests, of those tests, which have backlog items/tasks that are ready to be tested, etc.

Response:

Direct communication is the best method to indicate that a new feature is ready for testing, but the system can also help identify and track items as they are ready. Once all of the build tasks on a backlog item (aka story or requirement) are completed, the developer or lead will update the status of the backlog item to a 'Done' or, as some prefer, a 'Ready for Testing' status.

Those responsible for the testing can filter their My Home Summary page so that just those backlog items in the 'Ready for Testing' status are included in the view.

Notifications also provide another method to identify which items have been newly marked as 'Ready for Testing'.