Shiplight vs testRigor: Intent-Based Testing Compared

Shiplight vs testRigor: Intent-Based Testing Compared

Both Shiplight and testRigor promise the same thing: write end-to-end tests without code, and let AI handle the maintenance. Both use intent-based approaches instead of brittle DOM selectors. Both claim self-healing.

But they're built for different teams and different workflows. testRigor is designed for non-technical testers who want to write in plain English. Shiplight is designed for developers and engineering teams who build with AI coding agents and want tests in their repo.

We build Shiplight, so we have a perspective. This comparison is honest about where testRigor excels and where we think Shiplight is the better fit.

Quick Comparison

How They Work — Side by Side

testRigor: Plain English Testing

testRigor's core idea is that tests should be written from the end user's perspective in plain English. No selectors, no code, no framework knowledge.

A testRigor test looks like this:

login
click "New Project"
check that page contains "Project created successfully"
enter "My Project" into "Project Name"
click "Save"
check that page contains "My Project"

The platform interprets these instructions at runtime using AI and a proprietary language engine. It supports over 2,000 browser combinations, mobile apps (iOS and Android), desktop applications, and API testing.

Strengths:

• Lowest barrier to entry for non-technical users
• Broad platform coverage (web, mobile, desktop, API)
• 2,000+ browser combinations
• AI-powered test generation from recordings or descriptions
• Tests require 95% less maintenance than Selenium-based alternatives

Trade-offs:

• Tests live in testRigor's platform — not in your repo
• Plain English syntax still has conventions to learn
• Limited granular control for complex test scenarios
• Less developer-oriented than code-based or YAML-based tools
• Pricing starts at $300/month with 3-machine minimum

Shiplight: YAML Intent Testing in Your Repo

Shiplight takes a different approach. Tests are YAML files with natural language intent statements combined with Playwright-compatible locators. They live in your git repo, are reviewable in PRs, and run anywhere Node.js runs.

A Shiplight test looks like this:

goal: Verify user can create a new project
base_url: https://your-app.com
statements:
  - URL: /dashboard
  - VERIFY: Dashboard is visible with welcome message
  - intent: Click "New Project" in sidebar
    action: click
    locator: "getByRole('link', { name: 'New Project' })"
  - intent: Enter project name
    action: input_text
    locator: "getByPlaceholder('Project Name')"
    text: "My Project"
  - intent: Click Save
    action: click
    locator: "getByRole('button', { name: 'Save' })"
  - VERIFY: Project appears in the project list

Shiplight's MCP server connects directly to AI coding agents (Claude Code, Cursor, Codex), so the agent that builds a feature can also verify it in a real browser and generate the test automatically.

Strengths:

• Tests live in your repo — version-controlled, reviewable in PRs
• MCP integration with AI coding agents
• Self-healing via intent + cached locators for deterministic speed
• Built on Playwright for cross-browser support
• No vendor lock-in — YAML files are portable
• SOC 2 Type II certified with VPC deployment

Trade-offs:

• Web-focused (no native mobile or desktop testing)
• More developer-oriented — less accessible for non-technical testers
• Newer platform with a smaller community
• No self-serve pricing page

The Core Difference: Who Writes the Tests?

This is the fundamental divide between the two tools.

testRigor assumes non-technical testers write tests. The plain English syntax, visual recorder, and platform-hosted tests are all designed to make testing accessible without engineering skills. If your QA team doesn't write code and you want them to own test creation, testRigor is purpose-built for that.

Shiplight assumes developers and AI agents write tests. The YAML format, MCP integration, git-based workflow, and Playwright foundation are designed for engineering teams who want testing as part of their development loop. If your developers use AI coding agents and you want verification integrated into that workflow, Shiplight is designed for exactly that.

Neither approach is universally "better" — it depends on who owns testing at your company.

Test Ownership and Portability

testRigor

Tests are created and stored in testRigor's cloud platform. You write them in testRigor's interface, they execute on testRigor's infrastructure. If you decide to switch tools, your tests don't come with you — the plain English format is proprietary to testRigor's interpreter.

Shiplight

Tests are YAML files committed to your repository. They produce clean diffs, are reviewable in pull requests, and run via the Shiplight CLI anywhere Node.js runs. If you leave Shiplight, your YAML test specs remain as documentation of your application's expected behavior.

Why this matters: Testing is a long-term investment. Teams that have built 200+ tests over a year need to consider what happens if priorities change. With testRigor, those tests are locked in. With Shiplight, they're portable.

Pricing

testRigor

testRigor starts at approximately $300/month with a minimum of 3 virtual machines. All tiers include unlimited test cases and unlimited users. As test suites grow, additional machines can be added to reduce execution time. This per-machine pricing can scale significantly for large test suites running frequently.

Shiplight

Shiplight's MCP Server is free with no account required — AI coding agents can start verifying and generating tests immediately. Platform pricing (cloud execution, dashboards, scheduled runs) requires contacting sales. Enterprise includes SOC 2 Type II, VPC deployment, RBAC, and 99.99% SLA.

Honest assessment: testRigor wins on pricing transparency — you know what you'll pay before talking to sales. Shiplight's free MCP Server is a strong entry point, but platform pricing requires a conversation.

When to Choose testRigor

Be honest — testRigor is the better choice when:

• Non-technical testers own QA. If your testing team doesn't code and shouldn't have to, testRigor's plain English approach has the lowest barrier to entry.
• You need mobile and desktop testing. testRigor supports iOS, Android, and desktop apps. Shiplight is web-focused.
• You want broad browser coverage. testRigor offers 2,000+ browser combinations out of the box.
• You need API testing built in. testRigor includes API testing natively. Shiplight handles APIs via inline JavaScript in YAML tests.
• You want transparent pricing. testRigor publishes plans and pricing. Shiplight requires contacting sales.

When to Choose Shiplight

Shiplight is the better fit when:

• You build with AI coding agents. Shiplight's MCP integration connects to Claude Code, Cursor, and Codex — the agent verifies its own work in a real browser during development.
• You want tests in your repo. YAML test files live alongside your code, are version-controlled, produce clean diffs, and are reviewable in PRs.
• Developers own testing. If engineers are writing and reviewing tests, YAML in git is a natural fit. Plain English in a separate platform adds context-switching.
• You need enterprise security. SOC 2 Type II, VPC deployment, immutable audit logs, RBAC, and 99.99% SLA are available. testRigor offers SOC 2 but fewer deployment options.
• You want no vendor lock-in. YAML specs are portable. testRigor's plain English tests are platform-specific.
• You need cross-browser with Playwright. Shiplight runs on Playwright, supporting Chrome, Firefox, and Safari/WebKit. testRigor has broader combinations but uses its own execution engine.

Frequently Asked Questions

Can testRigor tests be exported?

No. testRigor tests are written in the platform's proprietary plain English format and executed by testRigor's engine. They cannot be exported as Playwright, Cypress, or Selenium scripts. If you leave testRigor, you'd need to recreate tests in your new tool.

Does Shiplight support plain English testing?

Shiplight uses YAML with natural language intent statements rather than free-form plain English. The format is structured (intent + action + locator) which makes it deterministic and reviewable, but it requires slightly more structure than testRigor's conversational syntax.

Which tool has better self-healing?

Both use AI to handle UI changes. testRigor re-interprets plain English instructions on each run. Shiplight uses cached locators for speed and falls back to AI intent resolution when locators break — a two-speed approach that's faster for stable UIs but equally adaptive when things change.

Can I use both tools together?

In theory, yes — testRigor for mobile/desktop testing and Shiplight for web E2E integrated with AI coding agents. In practice, most teams choose one primary tool to avoid maintaining two test ecosystems.

What is intent-based testing?

Intent-based testing describes what a test should verify in natural language rather than how to interact with specific DOM elements. Both Shiplight and testRigor use this approach, but implement it differently — testRigor with free-form English, Shiplight with structured YAML intent statements.

Final Verdict

testRigor and Shiplight solve the same problem — brittle, high-maintenance E2E tests — but for different teams.

Choose testRigor if non-technical testers drive your QA process, you need mobile and desktop coverage, and you want an accessible platform with transparent pricing.

Choose Shiplight if developers and AI coding agents drive your workflow, you want tests in your repo as reviewable YAML, and you need enterprise-grade security with no vendor lock-in.

The deciding question: who writes your tests? If the answer is "QA people who don't code," testRigor. If the answer is "developers and AI agents," Shiplight.

Get Started

• Try Shiplight's MCP Server — free, no account needed
• Book a demo
• YAML Test Format
• Best AI Testing Tools in 2026
• Documentation

References: Playwright browser automation, testRigor, SOC 2 Type II standard, Google Testing Blog