Stably

O que é Stably?

Stably is an AI-assisted QA platform for testing web applications. It turns plain-English scenarios into Playwright tests and supports planning, execution, and maintenance through a cloud interface, CLI, and CI workflows.

QA staff and product managers can contribute test coverage while engineers retain control of the code in their repositories. Stably proposes repairs when an application changes and provides evidence for investigating potential product bugs. Generated and repaired tests remain reviewable rather than changing silently. Review generated assertions, proposed repairs and failure classifications before using them to gate a release.

O que Stably pode fazer?

Structured test planning

Convert natural-language intent into steps, expected outcomes, and coverage hints. The planner highlights missing expectations and potential edge cases before code generation.

Portable Playwright code

Generate test files that work with standard Playwright tooling. Engineers can review Git diffs and edit selectors, assertions, and retries directly. Generated selectors favor role-based locators.

Visual authoring and recording

Build tests from plain-English steps or recorded browser actions in Stably Cloud. Bidirectional synchronization keeps visual edits and repository code aligned.

Concurrent browser execution

Run suites across browsers and environments in the cloud or CI. Execution results include screenshots, traces, and recordings, with failures grouped by root cause.

Reviewable test repairs

Propose updates to broken selectors and test steps as the application evolves. Flag likely product regressions for engineer review instead of treating every failure as test drift.

Team governance

Maintain an audit trail for generated and repaired tests, with role-based controls for approvals and rollout.

Casos de uso

“Turn product requirements into coverage”

QA staff and product managers can start from documents, tickets, or written test intent to define acceptance scenarios for engineering review.

“Check critical flows before release”

Exercise checkout, authentication, and onboarding journeys during CI builds, then use recorded evidence to investigate failures before deployment.

“Maintain an evolving test suite”

Teams updating interfaces can review proposed repairs and route likely application bugs to engineers, keeping test maintenance distinct from regression investigation.

“Expand testing across environments”

Teams with larger suites can run browser and environment combinations concurrently, then inspect grouped failures to prioritize investigation.

Perguntas frequentes

Do all test authors need to write code?

No. QA staff and product managers can author scenarios in plain English or record browser actions. Engineers can review and modify the resulting Playwright code.

Can the generated tests run outside Stably?

Yes. Stably generates Playwright code that lives in your repository and runs with standard Playwright tooling.

What plans are available?

Hobby costs $0 per month and includes $10 in monthly credits with up to one concurrent browser. Team costs $60 per month with $60 in credits and up to 50 browsers. Growth costs $250 per month with $250 in credits and up to 100 browsers. Enterprise has custom pricing, SAML/SSO, SLAs, and 24/7 support.

How is testing usage charged?

Credits cover browser time and AI tokens. Browser time costs $0.01 per minute; AI tokens cost $0.30–$15 per million, depending on the model. Hobby supports pay-as-you-go usage after included credits. Plans allow unlimited team members and cancellation at any time.