Skip to content
You're viewing the v2 docs. Looking for v1?Go to v1 docs
Docs
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

Testsigma & Arcus Docs

Docs, API reference, and release notes for Testsigma and Arcus. Ask a question across both, or pick where to start below.

Try asking

Products

Automate tests without writing code, so the people who know the application can test it. Write steps in plain English, or let Atto generate them from a Jira story, a Figma frame, or a prompt. Run them on web, mobile, desktop, Salesforce, and APIs, and let auto-healing fix locators that move.

Test management run by AI agents. Attach a Jira story, a Figma design, or a recording, and the agents write the test cases, automate and run them, file defects, and report how ready the build is. You accept what goes in, and rejected cases are tracked as gaps.

Fixes feed back into the caseWriteCopilotRecorderNLP stepsPlain English, no codeGenerateRequirementsDesignsFilesCases from what you haveExecuteAgenticCloudLocalParallel, wherever you runFixHeal locatorsAnalyze failuresReport bugsFewer red buildsShipRun test plansAnalyze resultsShare reportsResults your team can read

Five stages, one test case. Hover a stage to see what Testsigma does there.Build the steps yourself: prompt Copilot, record the flow in the browser, or pick NLP steps from the library.Point Atto at a requirement, a design, or a file, and it writes whole test cases for you to review.Run a plan agentically, on the parallel cloud grid, or on your own machines, with no grid to maintain.Auto-healing repairs a moved locator mid-run, the Analyzer says why a step failed, and Bug Reporter files it.Run the plan on every build, read the result, and share the report with the people waiting on it.

New here? Start with these three

Browse by topic

What Testsigma does, the objects you work with, and the shortest path to a passing test.

The agents that generate, run, repair, and explain your tests.

The four ways to build steps, plus elements, step groups, and test data.

Suites, plans, machine profiles, schedules, and reading a run result.

Dashboards and reports for coverage, flakiness, and release readiness.

Pipelines, trackers, and chat, wired to the runs your team already watches.

Gaps feed back into coverageAttachRequirementsDesignsCode changesWhat you already haveGenerateBy scenarioBy modulePending reviewCases you review, not writeReviewAccept casesTrack gapsGrow coverageAccepted work, trackedRunPlan tiersTest runsAutomated plansManual or automatedShipCoverageReadinessRelease gateEvidence for the call

Five stages, from a requirement to a release call. Hover a stage to see what Arcus does there.Attach the sources that describe the feature. QI Home reads them as context, so nothing is retyped.QI Home drafts the cases, including the edge cases a tired reader of the ticket would miss.Accept what is useful and drop the rest. Accepted cases land in your folders like any other case.Run a case yourself or let Copilot automate it. Either way the result lands in the same run.Every run rolls up into coverage by module and a readiness score you can take to the release meeting.

New here? Start with these three

Browse by topic

What Arcus does, the objects you work with, and where to start.

The AI workspace that reads your requirements and writes the cases.

Test cases, reusable step groups, and the data sets they read.

Turn accepted cases into automated ones, and explore what is missing.

Execute a run, track it in a plan, and report on the outcome.

Dashboards and reports for coverage, flakiness, and release readiness.

Works with what you already run

Get certified by Testsigma

Learn how Testsigma works, step by step, with courses and certifications in Testsigma Academy.

Sign in to Testsigma Academy

Was this page helpful?

Last updated: