QA metrics
Quality
Automation Coverage
MusesAcademy Product - Total test case automation coverage by platform · trend over 7 days
All tests
Automated share of all test cases
Automatable tests
Coverage counting only tests tagged “automatable”
Split by Testomat tag — cases without a platform tag aren't counted. “mobile” covers both iOS and Android.
Test Cases Traction
Draft backlog
Drafts: tagged “draft” now, however old · trend over 7 days
Updated existing test cases
Share of tests created over 7 days ago, not tagged “draft”, that were edited since · trend over 7 days
Updated = Testomat's last-edit time falls in the window, so a test edited twice counts once. Changes from an import from code count too.
Out of sync
Automated tests edited in Testomat since their last import from code · trend over 7 days
Testomat's own “Out of sync”: the code still has the old version until the test is reimported from code or the edit is rejected in Testomat.
Test runs
MusesAcademy Product - Finished runs labelled web or mobilePlatform (iOS / Android) · last 60 days, trend per 24 h
Runs and success rate
Success rate = passed of the tests that ran in finished runs; skipped tests didn't run and are left out
Flaky rate
Flaky = failed, then passed on a retry, of the tests that ran in finished runs
Testomat keeps one result per test even when it was retried: one that failed and then passed is marked “Success after retry” and counts as passed in the success rate too. A suite that doesn't retry failed tests never shows any.