Write, Run & Maintain testRigor Tests with Claude Code

Heather Brooks

Open-source skills that let Claude author plain-English tests, run them against your app through a secure tunnel, debug from real results, and keep your cloud test suite in sync — straight from your repository.

How it Works:Your Tests as Code, Driven by Claude

testRigor runs UI tests written in plain English on real cloud browsers. These Claude Code skills turn that into a tight development loop: your tests live as files in your repo, the testrigor command-line tool pushes them to a cloud test suite and runs them, and results come back as an exit code plus a JUnit report. Point a run at your deployed site — or at localhost, reached through testRigor’s secure tunnel.

Plain English, not selectors
Refer to what the user sees click "Sign in" never brittle CSS or XPath.

Tests as code
Test cases, reusable rules and variables are files you version alongside your app.

Run anywhere
The same tests run on local, staging or production — the URL is supplied at run time, never hard-coded.

The Test Language:Reads Like Instructions to a Person

click "Sign up"
generate a unique email, then enter it into "Email" and save it as "generatedEmail"
generate a unique name, then enter it into "Name" and save as "generatedName"
enter "PasswordSuperSecure" into "Password"
click "Submit"

# Verify the confirmation email has arrived
check that email to stored value "generatedEmail" was delivered

# Open the confirmation link or email
click "Confirm Email"
check that page contains "Email was confirmed"
check that page contains the string with parameters "Hello, ${generatedName}"

What’s Inside:Four Focused Skills

Each skill is a self-contained capability, so Claude loads only the one relevant to the moment — authoring, running, API steps, or the full loop.

Install:Set Up in a Couple of Minutes

You’ll need a testRigor account (for an API token), Node.js 18+, and Claude Code.

1. Install the testRigor CLI
   The skills drive this command-line tool.

   # Node.js 18+
   npm install -g testrigor-cli
   testrigor --version

2. Authenticate
   Generate a Personal Authentication Token in testRigor (your name → API Tokens), then export it so Claude and CI never hit an interactive prompt.

   export TESTRIGOR_API_KEY="your-personal-auth-token"

3. Add the skills to Claude Code
   Copy the skill folders into Claude Code’s skills directory — personal (every project) or scoped to a single repo. Claude discovers them automatically.

   git clone https://github.com/TestRigor/skills.git
   
   # personal — available in every project
   mkdir -p ~/.claude/skills
   cp -r skills/testrigor-* ~/.claude/skills/
   
   # …or project-scoped:
   # cp -r skills/testrigor-* <your-project>/.claude/skills/

Usage:Then Just Ask Claude

Point the CLI at a test suite, then describe what you want — Claude pulls in the right skill based on the task.

testrigor test-suite config --default < YOUR_SUITE_ID>

Write a testRigor test that logs in and checks the dashboard, then run it against http://localhost:3000.

My checkout test is failing — debug it from the JUnit report and fix it.

Seed data with a call api step, then verify the result in the UI.

# your app on :3000, then:
testrigor test-suite run --localhost --url "http://localhost:3000" \
  --test-cases-path "tests/**/*.txt" \
  --rules-path "rules/**/*.txt" \
  --explicit-mutations \
  --junit-report-save-path report.xml

Exit code 0 and failures=”0″ mean green — and Claude keeps fixing the test (or your app) and re-running until it gets there.

“We spent so much time on maintenance when using Selenium, and we spend nearly zero time with maintenance using testRigor.”

Keith Powe VP Of Engineering - IDT