Review execution results
Read successful, failed, and blocked tests together. Compare manual and automation results within the same testing scope.
Test Analytics
Understand the test results behind release confidence
Bring manual and automation results into one review. Follow run success, escaped defects, execution time, and resolution trends with your testing and delivery context.
Test Analytics
Manual and automation resultsTest execution overview
3 suites · Latest execution
- Test executions
- 424
- Successful
- 405
- Success rate
- 95.5%
- Execution time
- 18 min
| Suite | Passed | Failed | Blocked | Time |
|---|---|---|---|---|
| Checkout | 184 | 6 | 2 | 8m |
| Account | 126 | 3 | 1 | 6m |
| Billing | 95 | 5 | 2 | 4m |
Execution success trend
Successful executionsExplore the trend
14 failed and 5 blocked executions need review. Inspect the affected suites before assessing release readiness.
Switch between manual and automation workflows to inspect results and execution trends.
From signals to decisions
Read test success, defects, and time together
Keep execution volume connected to the testing outcomes and release questions your team needs to answer.
Follow escaped defects
Review issues found after UAT alongside your test strategy and execution history. Investigate where coverage or scenarios need attention.
Inspect time in the test cycle
Track execution and resolution time alongside outcomes. Identify where the test cycle creates delays or repeated work.
What to look at
Bring the testing sources into the same review
Connect manual and automated testing data with the projects and teams responsible for the work.
- Jira Xray and Zephyr
- Zephyr Scale Cloud
- TestRail and Azure DevOps Test
- Jenkins and supported API sources
- Manual test management
- Connect test management sources such as Jira Xray, Zephyr, TestRail, and Azure DevOps Test to bring execution and case results into the review.
- Automation and CI
- Bring Jenkins execution data and external automation results into the analysis through supported integrations and API-based collection.
- Team and project context
- Review results with consistent mappings and periods so differences between teams and projects can be investigated with context.
What to look at
Follow the result into the next test improvement
Use the metrics to decide what needs investigation, then check the testing outcome after making a change.
- Selected manual or automation workflow
- Suite and project scope
- Execution history and test results
- Escaped defects and resolution time
- Inspect the result mix
- Review failed and blocked executions alongside the total test activity. Identify the affected suite, project, and period.
- Follow defects beyond the execution
- Compare escaped defects and resolution trends with the test cycle. Discuss missing scenarios and the work needed to investigate them.
- Check progress after a change
- Review success, timing, and escaped defects again after updating the test strategy or automation workflow.
What does Test Analytics measure?
Review test execution results, success, efficiency, escaped defects, automation coverage, execution time, and resolution trends. Available measures depend on your connected sources.
Can we review manual and automated testing?
Yes. Oobeya brings manual test management and automation execution signals into the same engineering review.
Which test management sources can we connect?
Supported scenarios include Jira Xray, Zephyr, Zephyr Scale Cloud, TestRail, and Azure DevOps Test. Check the integration catalog and your environment’s connection requirements.
Can Jenkins and external automation results be included?
Yes. Oobeya supports Jenkins and API-based collection scenarios for external automation results. Review your result format and mapping during setup.
What do escaped defects help us understand?
They bring issues found after UAT into the test review so teams can investigate their scenarios, coverage, and release process.
Does a high test success rate establish release readiness?
Review success alongside failed and blocked cases, coverage, escaped defects, and the scope of the tests. The result mix is one input to the release decision.
See Oobeya in practice
Review testing with the release questions it supports
Walk through manual and automation results, escaped defects, and test timing with your testing workflow in mind.