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.

Opslane is framework-agnostic. Because it tests your app by opening it in a real browser — exactly the way a user would — it works with any technology that produces a browser-accessible interface. You don’t install a library, add a configuration file, or change a single line of your application code.

​
What Opslane needs

The only thing Opslane requires is a URL to your running application. This is typically a preview deployment that’s automatically created when you open a pull request. Opslane navigates to that URL, interacts with the app, and checks for regressions.
Opslane does not need access to your source code, build pipeline, or infrastructure. If a browser can load it, Opslane can test it.

​
Confirmed frameworks

Opslane has been tested and confirmed working with the following frameworks and stacks. This is not an exhaustive list — if your stack runs in a browser, it works.

​
Frontend frameworks

React

Create React App, Vite, and custom setups. Works with any state management library.

Next.js

App Router and Pages Router. Works with static exports and server-rendered apps.

Vue

Vue 2 and Vue 3. Nuxt apps are supported as well.

Svelte

Svelte and SvelteKit apps, including server-rendered routes.

Angular

Angular CLI projects and standalone component setups.

Any other frontend

Remix, Astro, Solid, Qwik, Ember — if it loads in a browser, it’s supported.

​
Backend-rendered frameworks

Ruby on Rails

Standard Rails apps with ERB, Hotwire/Turbo, and Stimulus setups.

Django

Django with Django Templates or any frontend layer served from the same app.

Flask

Flask apps with Jinja2 templates or a decoupled frontend.

Laravel

Laravel with Blade templates, Livewire, or a separate frontend.

Other backends

Express, FastAPI, Spring Boot, Phoenix — any backend that serves a browser UI.

​
Preview deployment platforms

Opslane works best when paired with a platform that automatically creates a preview deployment for each pull request. When a new PR is opened, the platform deploys the branch to a unique URL, and Opslane uses that URL as the test target.

Vercel

Opslane reads the Vercel preview URL from the PR deployment status automatically.

Netlify

Netlify deploy previews are supported out of the box.

Railway

Railway preview environments provide a stable URL per branch.

Render

Render preview environments work with Opslane without extra configuration.

Fly.io

Fly.io apps with per-branch deployments are supported.

Other platforms

Any platform that exposes a public HTTPS URL per pull request will work.
If your preview platform isn’t listed above, check whether it creates a publicly accessible URL for each PR. If it does, Opslane can use it. You can configure a custom deployment URL pattern in your Opslane dashboard settings.

​
No SDK or library required

Unlike some testing tools, Opslane requires zero changes to your application:
  • No SDK to install
  • No <script> tag to add
  • No test IDs or data attributes to add to your markup
  • No environment variables to set in your app
  • No CI workflow files to write
Opslane connects at the network and browser layer — entirely external to your codebase. Your application has no knowledge that it’s being tested.

​
Internal or private apps

If your preview deployment is behind authentication or a private network, Opslane will need a way to reach it. Options include:
  • Bypassing auth for the Opslane bot using a shared test account or a feature flag that disables auth for specific environments
  • Tunneling to make a local or VPN-protected app accessible to Opslane’s runners
Support for private networking and tunnel-based access is on the Opslane roadmap. Follow the open source repo for updates.