Failure-reason exclusion now lets release owners remove approved non-product failure categories from Perfecto reporting totals while retaining the original execution evidence. That matters when executive scorecards and CI quality gates need to reflect actionable product risk rather than recurring lab, infrastructure, or known-exception noise.
Make quality metrics more decision-ready
Perfecto 26.9 adds failure-reason exclusion to the Report Library, CI Dashboard, Insights, and Heatmap. Teams can filter selected reasons from reporting views and totals without deleting the related test results.
This creates a clearer separation between two important measures:
- Raw execution reliability: every result, including environmental and platform-related failures
- Release-quality signal: failures that should influence product readiness decisions
The control should not become a way to improve reported pass rates. Establish a governed list of eligible exclusions, assign ownership for each category, and review excluded volumes regularly. A sudden increase in excluded failures can indicate deteriorating test infrastructure, device availability, or integration health even when product metrics remain stable.
Extend iOS automation options with Playwright beta
Perfecto 26.9 introduces beta support for Playwright automation on real iOS devices running iOS 18 or later. The capability supports Playwright 1.62 through the Node.js SDK for JavaScript and TypeScript, using the same WebSocket connection model used for Android testing.
For teams standardizing web automation around Playwright, this offers a practical path to evaluate iOS browser coverage without maintaining entirely separate tooling patterns. It is beta support, so it should be introduced through a controlled pilot rather than immediately placed in release-blocking pipelines.
