Optimizing Test Suite

Test optimization empowers QA engineers and manual testers by providing improved test suite management through the "code to test list" feature. This feature enables testers to:

• Understand test-to-code relationships: Gain clear insights into which tests are linked to specific code sections. This knowledge helps identify whether tests are still relevant to the current codebase and functionality.

• Make informed decisions: Based on the code-to-test list, testers can assess whether individual tests require:

  • Adjustment: If code changes have altered functionalities or impacted areas previously covered by a test, the test might need adjustments to remain relevant.

  • Removal: If code sections associated with a test are no longer part of the codebase or have been drastically modified, the test might be obsolete and can be removed for optimal test suite efficiency.

• Maintain optimal test coverage: By analyzing the code-to-test list and strategically adjusting or removing tests, testers can ensure their test suite stays relevant, up-to-date, and effective in covering critical functionalities.

---

Step-by-Step Tutorial

1. Utilize the "Code to Test List" Feature

• On Test Optimization summary page, select the relevant app and date range.

• Click on the relevant test stage you want to review.

• Go to Builds, select the build with the code changes you want to explore and click Code to Test Mapping

• Utilize the "code to test list" feature to identify all tests linked to those specific code changes.

• Download as CSV file, for easier investigation.

2. Evaluate Test Relevance

For each listed test, carefully analyze its functionality and assess its continued relevance to the modified code sections.

3. Make Informed Decisions

Based on your analysis, determine whether each test:

• Needs adjustment: If the test needs modification to reflect the code changes, document the necessary adjustments and work with developers to implement them.

• Can be removed: If the test is deemed irrelevant due to code changes or functionality removal, initiate the process for its removal from the test suite, ensuring proper documentation and stakeholder communication.

4. Maintain Test Suite Documentation

Update your test suite documentation to reflect any adjustments or removals made based on the analysis of the code-to-test list.

By leveraging the "code to test list" feature, test optimization empowers testers to become proactive in managing their test suite, ultimately contributing to efficient, relevant, and high-quality testing processes.