This documentation is for Stably Classic. For the new Stably Web Editor, see Stably Web Editor Overview.
Why we recommend Stably 2.0
We recommend new projects start with Stably 2.0 because it is built on our SDK. The code-first foundation makes it more flexible, lets you version tests alongside application code, and prevents you from hitting a capability ceiling as scenarios grow more complex. See the Stably 2.0 capabilities for how AI editing pairs with SDK-level extensibility.- Use SDK-backed code to extend flows with custom logic and libraries.
- Keep tests in version control and reuse your existing CI/CD practices.
- Mix AI features with precise Playwright control when you need it.
- Stably Classic: Fully no-code with AI actions/assertions/auto-heal. Fastest for non-developers, but the UI surface can limit complex edge cases.
- Stably 2.0: SDK-backed with an AI/visual editor. Same AI features plus code-level extensibility, version control, and CI/CD alignment—best for long-term scale.
When Stably Classic is a good fit
- You want the fastest path to author tests with a visual, no-code editor.
- Your team prefers to avoid code but still wants AI assertions, AI actions, and auto-heal.
- You are already using Stably Classic.
When to choose Stably 2.0 instead
- You need deeper flexibility (custom data setup, complex conditionals, or integrations).
- You want tighter collaboration with engineers through pull requests and code reviews.
- You expect tests to evolve with your app and do not want to be constrained by a no-code surface.
Next steps
Start with Stably 2.0
Build new suites on the SDK-backed platform for maximum flexibility.
Use the Stably SDK
Write code-driven tests that combine AI features with Playwright control.
Run Classic tests
Keep existing Classic suites running and view results in the dashboard.