We believe in efficient documentation; this includes the identification of the core essence of the subject under test and not into deeper levels. For minimizing the risk of over-documentation, we ensure that our documentation is highly effective and requires minimal changes in case the requirements are changed.

We ensure this by the following techniques:

• Maintain test scenario diagram: A test scenario diagram represents the workflow or the tasks in a story defined at a high level (this never details the steps to execute these scenarios).
• The test scenario diagrams we prepare based on the communication with our clients, are sent for reviews. The review comments are incorporated and the approved documents are then used during each iteration the test execution phase.
• The most updated feedback sheets will be referred to by the project team.

If a different defect tracking tool (like Jira or Bugzilla or Mantis or Trac) is used then it should be integrated with the Test Management System. The integration is possible using third party utilities which establish proper communication channels so that whenever a test case is marked failed in Test Management System a corresponding defect is logged on the defect tracking tool. This will not need separate login to the defect tracking tool. Upon successful, new bugs can be logged from the Test Management System itself as it provides new interface to capture the necessary details detailing the bug and will communicate with the database of the defect tracking tool.