Test Management Part 2

• Test Case Review Process 


  a round of review and approval process before starting the test execution
• If we don't go for the review process, we may miss out some scenarios, remove accuracy of the test itself, and the test engineers may not review the software entirely.
• All the cases need to be sent for the review process only after the completion of writing the test case for the other person not to disturb the writer.
• Once the writer finished the test case, it needs to be sent to the other test engineer known as the reviewer for the review process.
• The reviewer opens the test case with the corresponding requirement documents and checks the correctness of the test case, proper flow, and maximum test coverage.
• If the reviewer found any mistake, he/she writes it in a separate document, which is known as review document, and sends it back to the writer.
• During this approval process, the Test Leader is kept in the loop so that the writer and reviewer will be serious in their jobs
• When the test cases are written, reviewed, and approved, it will be stored in one centralized location known as the Test Case Repository.
• Test Case Repository


  is a centralized location where all the baseline test cases are stored
• Template


  The reviewer checks whether the template is as per requirements for the product
• Header


  The following aspects must be checked:

  • All the attributes are captured or not
  • All the attributes are relevant or not
  • All the attributes are filled or not
• Once the test case is reviewed, the reviewer creates a review document, which contains the review comments.
• Test Execution Report


  This is all the attributes final document prepared by the test leader only when the entire testing process is completed
• Requirement Traceability Matrix (RTM)


  is a table-type document that is used in the development and testing of software applications to trace requirements.
• RTM is also known as Cross Reference Matrix
• Forward Tracing


  From requirements to Design / Coding
• Backward Tracing


  From Design / Coding to Requirements
• RTM is prepared after the approval of test cases and before the start of test execution
• Types of RTM

  Forward Traceability

  Backward / Reverse Traceability

  Bi-Directional Traceability
• Forward Traceability


  is used to ensure that every business' needs or requirements are executed correctly and tested rigorously.
• Backward / Reverse Traceability


  is used to check that we are not increasing the space of the product by enhancing the design elements, code, or testing things which are not mentioned in the business needs.
• Bi-Directional Traceability


  a combination of forward and backward traceability matrix, which is used to make sure that all business needs are executed in the test cases.