automated Playwright e2e tests

Octomind hosts and runs AI-generated end-to-end tests in standard Playwright code in the cloud.

create your first e2e tests

how do we use Playwright?

We generate and host Playwright tests you can run in parallel to whatever legacy framework you use.

The generated plain Playwright test code is yours. You can always use locally if you wish.

We use Playwright Trace Viewer to help you understand issues when tests fail.

[data-wf-bgvideo-fallback-img] { display: none; } @media (prefers-reduced-motion: reduce) { [data-wf-bgvideo-fallback-img] { position: absolute; z-index: -100; display: inline-block; height: 100%; width: 100%; object-fit: cover; } }

why do we use Playwright for end-to-end testing?

fast & reliable

Playwright tests multiple browsers simultaneously and runs headed or headless.

prevents flakiness

It includes features such as auto-wait and integrated VS Code debugging.

trace viewer

We can play back visual recordings to pinpoint specific interactions,

open source & free

Playwright has 59.2k stars and 3.3k forks as of February 2024.

dev community support

It's the most popular modern browser testing framework.

backed by Microsoft

Microsoft has a track record of providing open source dev tools

Playwright in Octomind end-to-end tests

diagram: use of Playwright in Octomind test discovery, generation, running, review and debugging process

use of Playwright in test discovery, generation, running, review and debugging process

Octomind automatically generates test case interaction chains using AI. We create the corresponding Playwright code on the fly and execute it against your pull request, by manual trigger or when scheduled, based on your preference. The Playwright code is standard and can always be downloaded and used locally.

For debugging, we use Playwright Trace Viewer to help you understand issues when tests fail. Our open-source Debugtopus tooling lets you run the Playwright tests locally, so you can set breakpoints to step through the code.

what functionality do our end-to-end tests include?

auto-discovery

Getting started is quick and easy. Let AI have a look at your app and discover tests to cover your critical flows.

auto-generation

Playwright test code is generated automatically as our AI agent mimics a human user to navigate the app.

test hosting

We host and run the Playwright tests. You can schedule test runs, trigger manually or from your CI/CD.

parallel execution

We run tests in parallel to reduce the waiting. We'll finish in 20 minutes or less, regardless of test suite size.

CI / CD

Easily integrate and run Octomind with GitHub, Azure, Jenkins, Vercel or via curl command.

local execution

Download the Playwright code and run our tests on your own machines against your local dev environment.

debugging

Use Playwright trace viewer and Debugtopus to run tests locally for easier debugging.

snapshots

Not familiar with selectors and DOM elements? Select elements in your page visually.

unlimited URLs

Create unlimited projects, test unlimited URLs. Just add a new project with a URL to be tested.

one-time-password

For improved security, you can log into Octomind using a one-time password.

VPN tunneling

To increase security, we can run your Octomind tests in a private network.

Slack integration

We can send test results from your test runs directly to Slack.

set-up and teardown

Do you have complex test cases that require set-up data? We got you covered.

COMING SOON

auto-fix

When you change UI, our tests will automatically adapt to the new user flow. No need to rewrite broken tests.

COMING SOON

flakiness prevention

We know the reasons tests fail and deploy strategies to mitigate flakiness. Including AI.

blogtopus: on Playwright, end-to-end tests and AI

50% developer rants, 50% tech news commentary, 100% cephalopod opinions on all things software. It's worth the read. Guaranteed.

Why we no longer use LangChain for our AI agents

When abstractions do more harm than good - lessons learned using LangChain in production and what we should’ve done instead.

Did you break your code or is the test flaky?

Flaky e2e tests are frustrating for QA and development teams, causing constant disruptions and eroding trust in test outcomes. A fail-safe checklist for how you can tell the difference.

The full-stack testing mindset

When done right, end-to-end tests are invaluable tools for comprehensively testing a backend. Working e2e tests is in everyone’s interest, whether you are on frontend, backend, engineering or QA. A call for collaborative effort.

backend testing

software development