Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.opslane.com/llms.txt

Use this file to discover all available pages before exploring further.

This page answers the most common questions about how Opslane tests your app, what it checks, how results are delivered, and what you need to get started. If something isn’t covered here, open an issue on GitHub or reach out through the Opslane dashboard.
Opslane opens a real browser, crawls your app, and runs the flows that matter. It checks that pages load, forms work, and nothing broke from the changes in the PR. You get a pass/fail result with screenshots of what the browser saw.You don’t specify what to test. Opslane figures out the critical paths by crawling your app on each run.
No. Opslane figures out what to check on its own. There are no Playwright scripts to write, no Cypress config to set up, and no test files to maintain. You connect your repo, open a PR, and get results.
You can. But most teams who try it abandon the test suite within six months because the tests get flaky and nobody has time to maintain them. Opslane is the practical answer to “I should write tests but I won’t.”There are no scripts to write, no flakes to chase, and no test infrastructure to babysit. If you want the coverage without the maintenance burden, Opslane is built for that.
If it runs in a browser, Opslane can test it. React, Next.js, Vue, Svelte, Rails, Django — it doesn’t matter what your backend or frontend framework is. Opslane interacts with your app the same way a user would: through the browser.
Yes. Opslane is open source — you can read exactly how it works. Your app runs in ephemeral sandboxes that are destroyed after each run. Nothing is stored between runs. Your source code is never transmitted to Opslane’s infrastructure; only the running app is reached by the browser.
Playwright and Cypress are test frameworks — tools for writing and running test scripts that you author and maintain yourself. Opslane is a service that runs on every PR with zero setup. You don’t write tests. You don’t maintain tests. You connect your repo and it just works.The key difference: Playwright and Cypress require a human to write the test logic. Opslane determines what to test automatically.
Every completed run includes a video recording of the browser session. You can access it directly from the PR comment Opslane posts on your pull request. Click the View run link in the comment to open the full results page, where the video, screenshots, and pass/fail breakdown are all available.
Opslane posts a comment on the PR with a failure status, screenshots of what went wrong, and a video of the browser session. If you have the opslane / browser-test status check configured as required in your branch protection rules, the merge button will be blocked until the issue is resolved.You can fix the code in your branch and push a new commit. Opslane automatically triggers a new run on the updated PR.
Yes. If a run fails and you want to re-trigger it without pushing new code — for example, if you suspect a transient issue — you can re-run it from the PR comment. Click Re-run in the Opslane comment on your pull request and a new browser session will start.
Opslane is free during early access. You can sign up at app.opslane.com and start testing PRs at no cost. Pricing details for after early access haven’t been announced yet.If you want to run Opslane on your own infrastructure, the open source version at github.com/opslane/verify is available at no cost.