Vera integrations

The tools Vera imports tests from, exports tests to, runs in CI, and is driven by over MCP. Each page lists what comes across, what does not, and how to set it up.

Test frameworks

Bring an existing suite in without AI credits, and take tests back out as code.

Playwright

Import .spec.ts files deterministically; export any test back as a Playwright spec.

Cypress

Convert cy command chains into Vera steps, one test per it() block.

WebdriverIO

Import WebdriverIO and JS selenium-webdriver specs; export as a Mocha spec.

Selenium

Java/Python via opt-in AI conversion, JS deterministically; export as pytest.

TestCafe

Turn fixtures, t.* chains and t.expect into Vera steps; export as a TestCafe suite.

API and traffic sources

Collections, specifications and captures that become API test steps.

Postman

Folders become tests and requests become api-request steps, variables intact.

OpenAPI

One test per tag, one status-checked api-request step per operation.

HAR

Recorded requests become api-request steps, one test per page, secrets stripped.

CI systems

Run Vera from a pipeline and gate the merge on real failures only.

GitHub Actions

The vera-run action: blocking failures fail the job, flakes and quarantine warn.

GitLab CI

A copy-in job: curl and sh only, JUnit in the MR widget, flakes warn.

Bitbucket Pipelines

The same gate script as GitLab, with JUnit in the Tests tab.

AI coding agents (MCP)

Let a coding agent run, inspect and repair Vera tests.

Claude Code

MCP wiring in one command, plus Vera's instructions for the agent.

MCP

Stateless Streamable-HTTP MCP at /api/mcp, free plan floor.

Start free