SpecSage

Validate web applications with human-readable test specs.

Write plain-language instructions. SpecSage executes them against a live browser, captures screenshots, and reports pass/fail results.

Instructions

  • Click sign in to go to the sign in page
  • Click on the email label
  • Enter turbo@turbo-spec.com
  • Click on the password label
  • Enter topsecret
  • Click log in

Expectations

  • You are on the news feed page
  • You see the text "create story", and dashboard in the header
  • You see your initials in the top right, "TU"

How It Works

  1. 1

    Write test instructions

    Describe what to test in plain language. No selectors, no brittle locators.

  2. 2

    SpecSage executes against your app

    A real browser loads your application and performs each instruction while capturing screenshots.

  3. 3

    Review pass/fail results

    Get deterministic, reproducible results with visual evidence for every assertion.

Why SpecSage

  • Deterministic tests

    Same input, same output. No flaky tests caused by timing issues or race conditions.

  • No selectors to maintain

    Instructions reference what users see, not implementation details. Refactor freely.

  • Screenshot-based validation

    Every assertion is backed by visual evidence. Debug failures in seconds.

  • Human-readable specs

    Test files that anyone on the team can read, write, and review.

Jump Your QA Efficiency by 10x

Test Spec

base_url: "http://localhost:4010"
max_steps: 11

instructions: |
  Click sign in to go to the sign in page.
  Click on the email label.
  Enter turbo@turbo-spec.com
  Click on the password label.
  Enter topsecret
  Click log in

expectations:
  - You are on the news feed page.
  - You see the text "create story", and dashboard in the header.
  - You see your initials in the top right, "TU".

Result

Verdict: PASS

Expectation 1: The page shows the heading text
"News Feed" (center top of main content).

Expectation 2: The header/nav shows "Dashboard"
(top header), and the stories section shows
"Create Story" (left story card).

Expectation 3: The top-right header shows initials
"TU" (button labeled "TU" at top right).

Steps: 7
Duration: 25 seconds

Use Cases

  • QA Automation

    Replace manual testing checklists with executable specs. QA engineers write tests without learning a programming language.

  • CI Validation

    Run SpecSage in your CI pipeline. Catch regressions before they reach production.

  • Pre-deployment Checks

    Validate critical user flows before every deploy. Ship with confidence.

Get Early Access

SpecSage is currently in private beta. Reach out to get early access.