The AI-native home for your QA team

sqale turns requirements into test cases, keeps every run and bug traceable, and gives you an agent that triages CI failures and tells you if it's safe to ship.

sqalehq.ai / checkout / agent
Write test cases for PROJ-142 · Checkout with saved cards and flag any gaps.
Reading PROJ-142 from Jira
Extracting 6 acceptance criteria
Finding edge cases and negative paths
Ask the QA agent anything…⌘K
Checkout · Saved cards
Coverage
0%
TC-141Checkout succeeds with a valid saved cardHigh
TC-142Expired coupon shows an inline errorMedium
TC-143Order total recalculates after removing an itemHigh
TC-144Payment retry after a declined cardHigh
TC-145Confirmation email includes the order IDLow

Fits the tools your team already uses

JiraGitHubSlackConfluenceNotionPlaywrightClaude & Cursor (MCP)

Product

Everything QA needs. Nothing it doesn't.

Plan, write, run and report in one place — with AI doing the busywork and your team staying in control of what ships.

Requirements in, test cases out

Import stories from Jira, Notion or Confluence. The agent reads acceptance criteria and drafts reviewable test cases — happy paths, edge cases and negatives — that land as drafts for your team to approve.

Valid saved card completes checkoutFunctional
Expired coupon shows inline errorNegative
Declined card offers a retryEdge case

Coverage you can see

Every requirement shows whether it's covered, partially covered or missing tests — before the release, not after the incident.

Checkout100%
Accounts82%
Search46%

Traceability from story to bug

Requirements, test cases, runs, CI results and bugs stay linked automatically, so every failure has a paper trail.

REQ-24

Saved cards

TC-141

Passed

Run #87

Release 2.4

BUG-31

Fixed

CI results, matched to your tests

Send JUnit or Playwright results from GitHub Actions or any CI. Results map to test cases, update run history and surface flaky tests.

Pass rate · last 12 CI runs2 flaky tests flagged

Manual runs that flow

Step-by-step execution with per-step results, retest history, and one-click bugs prefilled from the failed steps.

Bug reports with context

An embeddable widget captures screenshots, console and network logs, then files to Jira with everything attached.

API testing built in

Import an OpenAPI spec, assert on status, body and timing, run on a schedule, and get alerted in Slack.

How it works

From story to sign‑off in three steps

01

Connect

Bring requirements from Jira, Notion or Confluence, and link your GitHub repo for CI results.

02

Generate & review

The agent drafts test cases and plans. Your team edits, approves and organises them into suites.

03

Run & trace

Execute manually or from CI. Coverage, pass rates and bugs roll up to every requirement and release.

QA agent

Ask in plain English. Get answers with receipts.

The agent works across your projects with real tools — searching cases, reading CI runs, filing bugs and checking release readiness. Use it in sqale, on a schedule, from a webhook, or from Claude and Cursor through MCP.

  • Scoped to your project and your role — viewers get read-only tools
  • Runs on a schedule or from webhooks for hands-off triage
  • Connect Claude Desktop or Cursor with an MCP key
Is release 2.4 safe to ship?

2 critical bugs still open and 3 requirements without passing tests. Not yet — here is what blocks it.

Triage last night’s CI failures

Matched 4 failures to known bugs, flagged 2 as flaky, and filed 1 new bug with the stack trace attached.

Which checkout flows have no tests?

Gift cards and 3-D Secure have no coverage. I can draft test cases for both.

Security

Built for teams that ship to production

Your test data describes how your product works. We treat it that way.

Tenant isolation

Every request is checked against your workspace and project on the server — no data crosses between customers.

Roles that mean it

Admins, members and viewers, enforced on every action and every agent tool.

Secrets stay secret

Integration tokens and credentials are encrypted at rest with AES-256-GCM and never sent to the browser.

Guarded automation

Outbound requests are blocked from private networks, and secrets only go to hosts you configure.

Pricing

Start free. Upgrade when your team does.

Every new workspace gets a 30-day Pro trial. No credit card required.

Free

$0/ month

For trying sqale on a single project.

  • 1 project
  • 10 requirements
  • 100 test cases
  • AI test case generation ($1 of AI usage a month)
  • Manual test runs & bug tracking
Get started

Pro

Most popular

$99/ month per workspace

Everything in Free, without limits, plus:

  • Unlimited projects, requirements & test cases
  • $10 of AI usage a month
  • Jira Integration
  • Confluence Import
  • Notion Import
  • Slack Notifications
  • CSV Import / Export
  • Browser Widget
  • API Access
  • CI Run Tracking
  • Shared Run Reports
  • Traceability Matrix
  • Shared Step Library
  • Test Plans
  • Releases
  • Reports & Analytics
  • Custom Fields
  • API Tests
Start 30-day trial

FAQ

Questions, answered

Is there a free plan?

Yes. Free covers one project with up to 10 requirements and 100 test cases, including AI generation. New workspaces also get a 30-day Pro trial.

Which tools does it integrate with?

Jira Cloud (import stories, push and sync bugs), Confluence and Notion (import requirements and docs), GitHub (CI results and repo sync), Slack (notifications), and Claude or Cursor through our MCP server.

Can I bring my existing test cases?

Yes. On Pro, import CSV exports (including multi-line exports from TestRail, Qase or Zephyr) with columns matched by header name. Playwright spec files can be imported from your linked GitHub repo.

How does CI integration work?

Install the GitHub App and upload JUnit or Playwright reports as workflow artifacts, or POST JUnit XML to our API from any CI with a project API key. Results are matched to your test cases automatically.

Is my data used to train AI models?

AI features run on Anthropic’s API, which does not use API inputs to train models by default. Your workspace data stays isolated from other customers.

Can I control who sees and edits what?

Workspace admins manage members and settings. Projects have admin, member and viewer roles, and viewers get read-only access everywhere — including the agent.

Ship your next release with confidence

Set up a workspace in minutes. Import your first requirements and watch the agent draft the tests.