Limits
What the platform cannot do
The platform runs the tests that were written and reports what passed, failed or was healed. It does not prove that an application has no bugs. Healing applies to locator and layout changes; a changed behaviour fails the test and waits for a human decision. The platform does not replace exploratory testing, accessibility review or security testing.
Limits per capability
| Capability | What it does not do |
|---|---|
| Tests in plain English | Does not accept free-form prose without step structure; does not generate assertions that were not written. |
| Runs in CI | Does not block merges by itself; the branch protection rule is the team's decision. |
| Heals locator and layout changes | Does not heal a behaviour change; a changed outcome fails the test and goes to triage. |
| Triages failures | Does not file tickets without an integration and a human click; classification is a proposal. |
| Learns your product | Does not read production user data; sources are chosen and connected by the team. |
| Finds coverage gaps | Does not measure code coverage. |
| Parallel hosted runs | Does not run on the customer's own infrastructure unless the plan includes self-hosted runners (planned). |
| API steps | Does not replace load testing. |
Where the limits are set
- Healing rules: which changes are healed without a human and which wait for review.
- Triage output: the classification is a proposal.
- Roadmap: capabilities that are planned and not available.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.