Skip to main content
Free plan, no cardStart free

SELSmart test selection · updated 2026-11-10

Smart test selection tool: the smallest suite for a requirement

A requirements document or a Jira, Linear or GitHub issue in; scenarios scored by risk, the smallest set within a time budget, and a written reason per pick.

For: QA leads and developers who have to decide what to run before a release, product owners who want a requirement turned into testable scenarios, and teams in regulated work that have to show which clauses of a specification their tests touch.

acme-shop / checkout-flow.recIllustrative run
  1. REGRegressionPassed14 / 14 steps · 38.2 s
  2. LOADLoad · 200 virtual usersIn budgetP50 180 · P95 412 · P99 690 ms
  3. SECSecurity · OWASP Top 10 (2025)1 confirmed1 confirmed · 2 observed
  4. A11YAccessibility · WCAG 2.2 A and AA3 issues9 pages · VPAT draft ready
1 selector healed#pay-now-btn[data-test="pay"]Shown in the run

Capabilities

A requirements document in, scenarios out

Upload or paste a BRD, a specification or a user story. The platform extracts the requirements, classifies each one (functional, non-functional, business rule, acceptance criteria, constraint, assumption, dependency) and generates the test scenarios they imply, each with a confidence score.

Read more: A requirements document in, scenarios out

An issue as the requirement

Import a Jira, Linear or GitHub issue by its URL with a token used once and never stored; its title, body and acceptance criteria are analysed like a document. Nothing is written back to the tracker.

Read more: An issue as the requirement

The smallest suite within a time budget

A greedy set-cover selection keeps picking the scenario that adds the most new coverage per unit of time until the budget is spent, a method with a known optimality bound, and reports what was chosen and what was left out.

A written reason per pick

Each scenario explains itself: the risk factors behind it, where it sits on the L1 to L5 test ladder, an estimate of the mutations it would catch and a one-line summary. Suite quality is scored by mutation kill rate against a target.

What changed since the last version

Re-upload a revised document and the platform diffs it against the stored version at the requirement level, listing the nodes added, removed and changed. Only the delta needs new scenarios.

Coverage by clause, as evidence states

For a requirement that cites a standard, coverage is reported per clause as an evidence state, from a keyword match through a designed test to an executed one, never as one score and never as the word "compliant". BRD intelligence adds the vocabulary and bug hotspots of twenty industry verticals on the Team plan.

How it works

  1. Give it the requirementUpload or paste the document, or enter a Jira, Linear or GitHub issue URL with a token used once.
  2. Review what it extractedThe requirements by type, the scenarios each implies, the coverage matrix and the confidence per scenario.
  3. Set a time budget and selectThe set-cover selection returns the smallest set within the budget, with the reason for each pick and the list of what it left out.
  4. Run or carry it into your suiteRun the chosen scenarios against your recorded flows in the platform, or take the list into your own suite; there is no CI trigger yet.

What you receive, and what we do not do

Evidence ledger
Per scenario
Its risk factors, confidence score, test-ladder level, mutation estimate and a one-line reason.
Per selection
The scenarios chosen, what each covers, what was left out, and the time used of the budget.
Per re-upload
The requirement nodes added, removed and changed since the stored version.

Limits we state

  • There is no source-code impact analysis: it does not read a commit or a pull request and pick the tests that change can break. It works from requirements and issues.
  • There is no webhook from GitHub or GitLab and no CI trigger yet: the selection runs in the platform, and your pipeline runs the tests you export.
  • A local model can enrich the generated scenarios and degrades to the deterministic output when it is off or busy; nothing is sent to an external AI provider unless your team buys and switches on Work with AI for requirement analysis.
  • We publish no pipeline-time reduction figure; it depends on your suite, so measure it on yours.

Plans: Part of the AI tools: 40 AI tool runs a month on Solo Pro, 800 on Team and per contract on Enterprise; on Free as the AI tools single tool, $15 a month for 20 AI runs. BRD intelligence by industry vertical is on Team and Enterprise. See the metering table.

Questions buyers ask

What is a smart test selection tool?

Software that chooses, from everything you could run, the tests worth running now, and says why. Most tools of the kind key the choice to a code change. Dokimore keys it to a requirement: the document or issue describing what should work, turned into scenarios, scored and trimmed to a time budget with a written reason per pick.

Is this test impact analysis on a code change?

No. It does not read your repository, a commit or a pull request. Give it the requirement the change implements, as a document or an issue, and it returns the smallest scenario set that covers it. The "what changed" view diffs a re-uploaded document against its previous version, not a code diff.

Which inputs does it accept?

A requirements document you upload or paste, or the URL of a Jira, Linear or GitHub issue with a token that is used for one read and never stored. Other issue trackers are refused as unsupported, and private network addresses are blocked.

Does the AI see my requirements?

Generation and scoring are deterministic. A local model on the platform can enrich them, and it degrades to the deterministic output when it is busy. Nothing is sent to an external AI provider unless your team buys and switches on Work with AI for requirement analysis, in which case the redacted text goes to Anthropic’s Claude models with every call logged.

Try it on your own application

The Free plan asks for no card and runs for 14 days after the trial. Or bring one flow from your product and we record it live.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India