<aside> 💡

Example data showing typical insights a Fractional QA Team provides to product and engineering leadership.

</aside>

Overview of This Month

Test Suit Size

<aside> 💡

What this section shows

The total number of manual and automated tests protecting the product.

• Not all manual test are executed each release.
• Manual test cases naturally grows as new features added.
• A growing number of automated testing can keep up or even increase test automation ratio (Automated tests / All tests (%) ) </aside>

• After the pilot implemented 9 additional new type of automated tests (Reference Data Tests) with quicker ROI:

Updated Test Automation ROI Estimates

<aside> 💡

What this section shows

This chart estimates how long it takes for each test type to pay back its implementation cost through reduced manual testing.

Taken into the estimation calculation:

• initial test automation implementation time
• regular manual execution time
• ongoing test automation maintenance costs
• more frequent execution of automated tests (quicker quality feedback) - estimate calculates with a modest 2x efficiency gain </aside>

API/E2E test:

• ROI reached in 10 months (initial implementation overhead + ongoin maintenance ≥ if we would executed regularly manually)
• Broad functional coverage
• Longer ROI but significant long-term value

Reference Data API test:

• ROI reached in 4 months (initial implementation overhead + ongoin maintenance ≥ if we would executed regularly manually)
• Cover niche areas, limited coverage
• Rapid value delivery