Test documentation [Mandatory]

Test documentation describes the process, objectives, and results of software testing. It can also include information on the environment, setup, and configuration required to perform testing. Test documentation is used to communicate the details of a test plan or strategy to stakeholders, developers, and testers. Test documentation includes:

• A test strategy is a document that describes the software testing approach to achieve testing objectives. This document includes information about team structure and resource needs along with what should be prioritized during testing. It should include details of how the various types of testing should be performed including functional testing, performance and security testing.  A test strategy is usually static as the strategy is defined for the entire development scope.
• A test plan is a brief document that  describes what should be tested at a given moment. In the agile methodology, a test plan can be defined for each sprint.  This document should contain:
  ○ the list of features to be tested
  ○ testing methods
  ○ timeframes
  ○ roles and responsibilities
• Test case documentation is a set of detailed actions/ scenarios and expected results to verify each feature or functionality of a product. Test case specifications are based on the approach outlined in the test strategy and test plan.
• Test reports -  test reports list of tests that have been run at a particular time. It represents what tests are completed and how many have passed or failed. It also includes a list of issues which have been identified as part of the testing process.