FREEDOM251

Freedom251 › Visual Regression Testing Software

TestivAI OSS

Free plan Self-hosted

Visit TestivAI OSS Alternatives Pricing

TestivAI OSS's own site

What TestivAI OSS is

TestivAI OSS is a self-hosted tool for visual regression testing that compares screenshots with DOM snapshots to explain changes. Its analysis combines pixel differences, DOM structure, computed styles and element attribution to help distinguish rendering noise from other differences. Captures can freeze animations, hide the caret and wait for web fonts. Teams can set a maximum difference percentage or pixel budget, and optionally auto-pass noise identified through DOM analysis. Integrations include Playwright, Selenium, WebdriverIO and Ruby Capybara/RSpec, plus an experimental Java Playwright adapter. Cypress, Puppeteer and Robot Framework use the Witness CLI on Chromium, which the maker labels experimental. GitHub Actions can post reports to pull requests and support baseline approvals through a PR comment; workflows are also documented for GitLab CI, CircleCI, Jenkins and Buildkite. Screenshots, DOM snapshots and diff images are stored locally, and the optional MCP server connects clients such as Claude Code, Cursor or Copilot to results using the user's model. Reports are neutral checks by default, with optional hard failures. The MIT-licensed core costs nothing and needs no account or API key.

Who it suits

TestivAI OSS suits teams seeking locally run visual regression checks in their browser-testing and CI workflows. It may also suit developers who want optional AI-agent access to structured results through an MCP client.

What it does well

  • Screenshots and DOM data stay stored locally
  • No account or API key required
  • Supports several testing frameworks and CI systems
  • Teams can choose whether visual changes fail checks

What to know first

  • Java Playwright adapter is experimental
  • Witness CLI browser integration is experimental

Plans

PlanBilled and limitsPrice
TestivAI OSSMIT-licensed core · no account or API key required · runs locallyFree

As testiv.ai lists them, read 8 Oct 2026. The maker's own page has the final word.

Getting started

  1. Open the TestivAI website.
  2. Use the MIT-licensed core locally; no account or API key is required.
  3. Integrate it with Playwright, Selenium, WebdriverIO, or Ruby Capybara/RSpec.
  4. For CI, use GitHub Actions or the documented GitLab CI, CircleCI, Jenkins, or Buildkite workflows.

Verdict

TestivAI OSS combines screenshot and DOM analysis with local storage and configurable reporting. Its experimental integrations are worth noting when choosing a workflow.

Questions

Does TestivAI OSS have a free plan?

Yes. The TestivAI OSS plan is listed as free, and the maker describes the MIT-licensed core as free forever.

Does it require an account or API key?

No. The core runs locally and requires neither an account nor an API key.

Where are screenshots and diff data stored?

Screenshots, DOM snapshots, and diff images are stored locally; the maker says nothing is uploaded.

Which test frameworks are supported?

Integrations include Playwright, Selenium, WebdriverIO, and Ruby Capybara/RSpec, plus an experimental Java Playwright adapter. Cypress, Puppeteer, and Robot Framework use the Witness CLI on Chromium, which the maker labels experimental.

Can it work with CI and pull requests?

GitHub Actions can post visual reports to pull requests and support baseline approvals through a PR comment. The maker also documents workflows for GitLab CI, CircleCI, Jenkins, and Buildkite.

Is TestivAI open source and usable commercially?

The maker describes TestivAI as MIT-licensed and says it can be used in commercial products.

Facts from TestivAI OSS's own pages

AI agents
The optional MCP server connects Claude Code, Cursor, Copilot, or another MCP client to structured results and diff explanations using the user's model. · testiv.ai, 8 Oct 2026
Analysis
It combines pixel differences, DOM structure, computed styles, and element attribution to distinguish likely rendering noise from changes. · testiv.ai, 8 Oct 2026
Capture
Captures are stabilized by freezing animations, hiding the caret, and waiting for web fonts. · testiv.ai, 8 Oct 2026
CI integration
GitHub Actions can post visual reports to pull requests and support baseline approvals through a PR comment. · testiv.ai, 8 Oct 2026
Frameworks
Available integrations include Playwright, Selenium, WebdriverIO, and Ruby Capybara/RSpec, with an experimental Java Playwright adapter. · testiv.ai, 8 Oct 2026
License and price
The maker describes TestivAI as MIT-licensed, free forever, and usable in commercial products. · testiv.ai, 8 Oct 2026
Maintenance
The maker says TestivAI is built by solo developer Budi Sugianto and that there is no company behind it. · testiv.ai, 8 Oct 2026
Notable limit
Cypress, Puppeteer, and Robot Framework use the Witness CLI on Chromium; the maker labels the browser integration experimental. · testiv.ai, 8 Oct 2026
Other CI
The maker documents CI workflows for GitLab CI, CircleCI, Jenkins, and Buildkite using the same general capture and compare workflow. · testiv.ai, 8 Oct 2026
Privacy
Screenshots, DOM snapshots, and diff images are stored locally, and the maker says nothing is uploaded. · testiv.ai, 8 Oct 2026
Purpose
TestivAI performs visual regression testing by pairing screenshots with DOM snapshots and layered analysis to explain changes. · testiv.ai, 8 Oct 2026
Report behavior
Visual changes are reported as a neutral check by default, and teams can enable hard failures if they want them. · testiv.ai, 8 Oct 2026
Support
The maker lists [email protected] as its contact email. · testiv.ai, 8 Oct 2026
Tolerances
Users can set a maximum difference percentage or pixel budget and optionally auto-pass rendering noise identified by the DOM analysis. · testiv.ai, 8 Oct 2026

Where TestivAI OSS stands on Freedom251

Look at these too