Guide 30
A failure triage loop that takes minutes, not mornings
Read a red run, re-run just the failed tests from the composer, and decide when to re-run, regenerate, or fix the app.
GuideBring your own model: custom LLM endpoints in self-hosted TestVibe
Point self-hosted TestVibe generation at your own OpenAI-compatible endpoint, keep prompts inside your network, and configure it right.
GuideDebugging failures with Playwright traces
How to read Playwright traces in TestVibe (timeline, DOM snapshots, console, network) to find why a test failed, plus the Debug with AI shortcut.
GuideDo you know what your tests actually cover?
How TestVibe maps AI-derived app areas against your existing tests so untested parts of your app surface first.
GuideExtending generated tests with plugins
What TestVibe plugins are, the built-in catalog, how to enable them per project, and when a plugin beats a workaround.
GuideFrom one sentence of intent to a drafted test suite
Give the TestVibe Assistant an intent, and it explores your app, verifies behaviors, and drafts ready-to-run feature specs you review and accept.
GuideGenerating tests against the app on your machine.
Point TestVibe at your local dev build, capture flows in your own browser, and generate tests that run before you deploy.
GuideGetting started with TestVibe: from sign-up to your first passing test
A hands-on walkthrough: sign up, create a project, describe a flow in plain English, let AI generate a Playwright test, run it in the cloud, read the trace.
GuideHow TestVibe credits work
What consumes TestVibe credits, how monthly and purchased credits are applied, where to check usage, and what happens when you run out.
GuideKeep your tests in your repo: two-way Git sync with TestVibe
Mirror your TestVibe test files to GitHub, GitLab, or Azure DevOps — edits flow both ways, conflicts stay explicit, and your tests live next to your code.
GuideOne suite, three environments
Point the same TestVibe features at dev, staging, and prod using a project URL strategy, shared variables, and the right run scope per environment.
GuideOrganizing a growing test suite with features and groups
How to structure a TestVibe suite with atomic features and readable groups, plus naming conventions that stay navigable past 100 features.
GuidePut your test suite on autopilot with TestVibe Automations
Schedule test suites, chain runs on events, and get AI root-cause triage on failures — a practical guide to TestVibe Automations.
GuideReading a run: how results are organized
How a TestVibe run detail is structured — run vs scenario status, per-configuration rows, and the artifacts attached to each scenario.
GuideRecording flows in your own browser
Use the TestVibe recorder browser extension to capture a real browser journey and turn it into reviewable Gherkin and a runnable test.
GuideRunning one suite across browsers and viewports
How Playwright run configurations work in TestVibe, when a run fans out per config, and how to read the per-config results.
GuideSelf-hosting TestVibe on your own infrastructure
What the self-hosted edition runs, how the offline license works, and when on-prem beats the cloud.
GuideTelemetry: watch your app between test runs
Stream server CPU, memory, sessions, and errors from your real app next to your tests, then turn a telemetry signal into a covering test.
GuideTest data that never collides: the unique token
Why fixed test data breaks on repeat and parallel runs, and how the {{unique}} token gives every run its own fresh values.
GuideTest notifications your team will not mute
How per-user channels, failure-only filtering, and per-category controls keep TestVibe alerts signal instead of noise.
GuideTesting apps that are not on the public internet
How to run cloud browser tests against private, staging, and localhost apps using a tunnel, without opening inbound firewall ports.
GuideTestVibe from the terminal: the CLI, REST API, and MCP server
Drive TestVibe without the UI — create an API key, script the testvibe CLI and REST API, and let AI agents run your tests over MCP.
GuideTestVibe inside Visual Studio
The TestVibe extension for Visual Studio 2022 puts coverage, runs, features, and automations in tool windows next to your code.
GuideThe TestVibe assistant: ask your test suite questions
A practical guide to the in-app assistant, explaining failures, running ops actions, and suggesting the next tests to write.
GuideVariables and secrets: keeping credentials out of your specs
How to store login credentials, API tokens, and config in TestVibe, reference them from Gherkin, and rotate them without leaking values.
GuideWhere Gherkin fits in TestVibe
How the Gherkin spec works as the readable contract between what you describe and the Playwright code TestVibe generates.
GuideWhere your screenshots, videos, and traces live
How TestVibe captures run artifacts per scenario, where to find and download them, and how the workspace storage quota and retention work.
GuideWiring TestVibe into your CI pipeline
Trigger TestVibe runs from CI with the CLI or REST API, wait for the result, and fail the build when a test fails.
GuideWorkspaces, members, and roles
How personal and team workspaces work in TestVibe, how to invite members, what each role controls, and how teams organize projects.
GuideWriting test descriptions the AI nails on the first try
How to phrase natural-language behavior so TestVibe generates a passing Playwright test without a second pass.
Walkthrough 2
Load testing your web app with TestVibe
A practical walkthrough of TestVibe load tests: configure users and duration, run against your app, and read the live latency and error-rate charts.
WalkthroughTesting email OTP and magic-link flows with the MailSlurp plugin
Use disposable inboxes and virtual numbers to read one-time codes, magic links, and SMS codes so a test can finish a real login.
Deep dive 4
Browser VUs vs protocol VUs: choosing your load-test weapon
When to reach for protocol virtual users, when to spin up real browsers, and how to design k6 scenarios that answer the question you actually have.
Deep diveFrom plain English to Playwright: how TestVibe generates tests that actually pass
How TestVibe turns a plain-English description into verified Playwright code: Gherkin drafting, live exploration, web-first assertions, and regeneration.
Deep diveFrom production error to fix PR, drafted by the assistant.
How TestVibe's Debug with AI carries a failing test from diagnosis to a drafted pull request against your connected repo.
Deep diveWeb-first assertions: the end of sleep(5000).
How Playwright's auto-retrying expect() matchers replace fixed waits, with before/after code and the misuse patterns that reintroduce flake.
Best practices 9
E2E testing React SPAs without losing your mind
SPA-specific E2E pitfalls — hydration, client routing, virtualized lists, optimistic UI, portals — and Playwright patterns for each.
Best practicesForm testing beyond the happy path
Validation states, error recovery, keyboard-only completion, file uploads, and autofill quirks — with Playwright sketches and a checklist.
Best practicesLocators that survive a redesign
A resilience hierarchy for Playwright locators, with code for each rung and the honest case for when data-testid is the right call.
Best practicesResponsive testing: when mobile emulation lies
What browser viewport emulation actually reproduces, what only breaks on real touch devices, and how to pick a viewport matrix you can afford to run.
Best practicesStrategies for testing 2FA and OTP
Three ways to automate login flows that send a one-time code, and the security trade-offs of each.
Best practicesTest data management for E2E suites
Seeding, per-run isolation, unique values, and cleanup strategies that keep end-to-end suites from flaking on shared data.
Best practicesTesting login, sessions, and everything auth
Patterns for testing authentication reliably — dedicated identities, session reuse, expiry, OAuth, and the lockout traps that flake suites.
Best practicesThe nightly regression playbook
A concrete nightly setup — what to schedule, failure-only alerts, a morning triage ritual, and how to keep the night green.
Best practicesWhy your tests flake (and what actually fixes it)
The five real root causes of flaky end-to-end tests, ranked, with concrete fixes and a clear line on what auto-waiting does and doesn't solve.
Concepts 9
Do you actually need Gherkin?
An honest look at when Given/When/Then earns its place and when it is just ceremony, with alternatives.
ConceptsHow much end-to-end testing do you actually need?
The testing pyramid revisited for 2026 — what E2E is uniquely good at, where unit tests win, and a sane ratio.
ConceptsMonitoring and testing are the same loop.
Prod telemetry finds what your tests missed; tests stop what telemetry found. How to close the loop so each one feeds the other.
Conceptsp95 is a promise: reading load-test results like an SRE
How to read latency percentiles, VU ramp patterns, and error budgets so a load test tells you the truth about your app.
ConceptsPlaywright, Cypress, Selenium in 2026: an honest comparison
A fair look at the three major browser-automation tools — architecture, waiting model, browser coverage, parallelism, and when each is the right choice.
ConceptsShift-left without the slogans.
What actually changes when developers own end-to-end tests — PR-time suites, feedback budgets, and who fixes the red test.
ConceptsShould you trust a test an AI wrote?
The honest answer is no, not on faith. Trust in a generated test comes from running it, plus a human reading the spec.
ConceptsThe real cost of a test suite is maintenance.
Authoring a test is a one-time cost. Keeping it green as the app changes is the recurring one — and it dominates the budget.
ConceptsVisual regression vs functional testing: not either/or
What functional tests catch that pixel diffs miss, where visual regression earns its keep, and how to run both without drowning in noise.