Test automation coverage
Know exactly how many of your tests run automatically. The board tracks automation coverage by suite and updates the numbers after every test run. You choose the next area to automate and report progress with real numbers.
Trusted by over 500 forward-thinking companies
How test automation coverage works in Testomat.io
1. Link
Connect tests to code
Import tests from code
Attach code to tests
Sync tests with code
2. Mark
Label remaining tests manual
Assign the manual status
Tag tests without code
Count hand-written tests separately
3. Calculate
Divide automated by total
Calculate the automated percentage
Compare automated with total
Get the coverage percentage
4. Aggregate
Combine suite figures
Sum all suite percentages
Build the project percentage
Merge suites project-wide
How test automation coverage can help?
Coverage data works at every scale. Small teams find their first tests to automate, and large projects report exact numbers to stakeholders.
Startups & small teams
Learn where automation stands today and choose the tests to automate next.
Instant baseline
See what's automated from the start.
Quick wins
Find low-effort tests to automate next.
Saved time
Spend manual effort on complex cases.
Clear focus
Skip guesswork on what to test.
Mid-sized products
Track coverage for every suite and align the whole team on automation priorities.
Suite progress
Watch coverage grow suite by suite.
Coverage gaps
Surface folders with low automation.
Aligned priorities
Automate what matters to the release.
Shared view
Keep QA and devs on one page.
Enterprise projects
Measure coverage across large test suites and report exact numbers to stakeholders.
Coverage scale
Single view across large test suites.
KPI data
Objective numbers for stakeholders.
Effort result
See what each automation gain cost.
Team metrics
Compare coverage between projects.
Testomat.io test automation coverage features
Automation coverage board
The board shows the automation progress of your project as a percentage, with exact numbers for each suite. You see which areas run on automation and which still need work. The team plans automation with real numbers and shares the progress with a link.
- Automation percentage per project.
- Breakdown by suites.
- Automated and manual test counts.
- Shareable link to every board.
Testing analytics
Separate boards list flaky and slow tests. Two more boards show tests that always fail and tests that never ran. You find weak tests without reading logs, so the suite stays reliable and the team trusts the reports.
- Flaky tests board.
- Slowest tests board.
- Ever-failing tests board.
- Never-run tests board.
Automation metrics
Timelines and custom charts track coverage and test metrics over any date range. You see how the numbers change and follow the metrics your team defines. The charts support quarterly planning and prove the value of automation to management.
- Timelines for coverage and failures.
- Custom date range for analytics.
- Custom charts with own queries.
- Chart export to PNG, SVG, CSV.
User stories coverage
Testomat.io links tests and suites to user stories and builds a traceability matrix. Each story shows its tests and runs, and AI suggests missing tests for a requirement. You add the missing tests before the release.
- Tests and suites linked to user stories.
- Test coverage visible in Jira.
- User stories traceability matrix.
- AI review of requirement coverage.
Why teams choose Testomat.io test automation coverage
Clear progress
See automation percentage instantly.
Folder-level view
Coverage by folder and suite.
Gap detection
See suites with low automation.
Priority tracking
Check that strategy meets goals.
Better decisions
Support KPIs and planning.
Start working with Testomat.io today
Import your automated tests and see the automation percentage for every suite.
Import tests
Link to manual tests
Track coverage
What clients say
Recent reviews
“Excellent customer support”
Customer support is always prompt and high-quality. It's also great to see that user feedback is considered when developing new features. The team makes an effort to provide overviews of new features and keeps users informed about the latest updates.
4/5
“The Best TMS for Our QA Team!”
Our 15-person QA team has used Testomat.io daily for over two years. After comparing tools like TestRail, it stood out in both features and pricing. It’s affordable yet powerful. Jenkins integration works seamlessly, even manual testers can run tests easily. The clean UI speeds onboarding, improves collaboration, and saves time. We’ve recommended it widely, and others love it too.
5/5
“Testomat.io makes daily testing so much easier”
I’ve used Testomat.io daily for over two years, and it’s the best TMS I’ve worked with. Compared to tools like TestRail, it offers more features at a better price. Jenkins integration is seamless, even for manual testers. The UI is clean and easy to learn. It speeds up workflows, improves transparency, and makes team collaboration much smoother.
5/5
“Very convenient platform for managing test cases”
The platform is convenient and intuitive to use. I’ve been using it long enough to say it’s very user-friendly. It’s clear that the team is constantly working on and improving the platform.
5/5
“Great tool for creating and managing manual test cases efficiently”
As a Manual QA, I use Testomat.io to create and manage test cases with ease. The interface is intuitive, making onboarding simple. Test plans, runs, and results are well-structured in one place. Tagging helps organize cases efficiently. AI features speed up test creation. It keeps workflows transparent, improves collaboration, and reduces routine work.
5/5
“Testomat.io has been a great tool for managing both automated and manual tests in one place”
I really like how easy it is to integrate with frameworks and CI/CD tools, and the real-time reports with screenshots and analytics save a lot of time. Overall, it makes collaboration in the team much smoother and keeps testing well-organized.
5/5
Frequently asked questions
What is test automation coverage?
Test automation coverage is a metric that shows what percentage of your tests are automated, measured as a ratio against manual tests and broken down by folders and suites. It lets a QA manager track how far the automation effort has progressed across a project.
How is the automation coverage percentage calculated?
It is the ratio of automated tests to total tests in a given part of the project. If a suite has 16 tests and 5 are automated, the coverage for that suite is 31 percent. The board rolls these figures up by folder and suite.
Can I filter the Automation Coverage table?
Yes. You can sort alphabetically, by suite order, by the number of automated tests from largest to smallest, and by the percentage column from higher to lower or the reverse, so you can focus on the areas that matter most.
Should I aim for 100 percent automation coverage?
No. Total automation is rarely the goal. What matters is that automated tests find defects as effectively as the manual tests they replace. Some checks are better left manual, so coverage is a guide for prioritizing, not a target to max out.
Why does test management need a coverage metric?
It gives QA managers an objective starting point to evaluate the automation initiative, find gaps in the test plan, check that testing priorities are being met, and report KPIs on the effort and payoff of automation.
