Doctests is an AI platform for generating and stabilising Playwright tests. The repo audit (Audit Flash) uses the same engine, but it stays a Services engagement — it will not be a feature of the public SaaS. The self-service console arrives in beta in 2027. Until then, the engine powers Services work.
The Doctests engine speeds up Services work: scans and reports for Audit Flash (an internal tool, not the future SaaS), generation for Setup, and CI ingest for the flakiness audit. You get the code on your GitHub. You do not need the SaaS to run your tests.
See the Services offersThe web console will cover Playwright generation, flakiness observability, and coverage expansion, in self-service. There is no repo audit in the SaaS: Audit Flash stays a human engagement, powered by the engine internally. Setup and Sprint clients get one free month of access at launch.
Become a design partner“Built · via Services” means it already runs in the engine, including the repo audit, which stays a Services engagement. “Public SaaS” means Playwright generation and flakiness in self-service — beta 2027. Audit Flash will not be part of the SaaS.
Self-service web app: Playwright generation, flakiness tracking, and coverage expansion. The repo audit (Audit Flash, scan, PDF) stays a Services engagement — outside the public SaaS.
User management, roles, permissions, and project spaces across several teams.
A maintainable Playwright TypeScript baseline — delivered today on a Setup engagement, and available self-service in the SaaS later.
Analysis of new flows added to your application, and automatic proposals for the missing scenarios — a SaaS console feature.
Intelligent refactoring of existing test suites, to improve readability, maintainability, and stability.
Human engagements (SDET), powered by the Doctests engine: code diagnosis, a flaky audit with CI ingest, Setup, and Sprint. This is not the SaaS. It is how you use the engine today.
CI report ingest and a ranking of unstable tests — used in the in-depth audit today, and a SaaS dashboard in the 2027 beta.
Automated analysis of unstable tests, with a root-cause explanation and fix recommendations.
Long-term tracking of test stability across several applications and teams.
Detection of broken selectors, and automatic fix proposals.
User stories and acceptance criteria used to enrich test-scenario generation.
GitHub Actions, GitLab CI, Jenkins, CircleCI, and Azure DevOps.
Optional creation of test plans and executions directly in Jira.
See which user stories are covered, and which scenarios are missing.
Functional specifications and product documentation used to enrich generation.
Native sync with the main test-management tools.
The public SaaS is in a design-partner beta. You can already use the engine through a Services engagement, or help prioritise the console by joining the 2027 beta.