1. Docs
  2. Use cases
  3. Use cases
  4. How do I get test cases from a requirements document?

How do I get test cases from a requirements document?

In SmartestQA, select a module folder in Analyze, attach your document on the Import tab and click Analyze with AI. The AI proposes requirements, sub-requirements and scenarios, writes steps that use your recorded actions where they match, and creates the requirements in Analyze and the linked test cases in Automate when you click Create.

12 min read Updated CustomersAdmins

In short

On this page you can

  • Turn a Word, PDF, text, Excel file or screenshots into requirements, sub-requirements and scenarios.
  • Edit the outline before any step is written.
  • Get steps that reuse your recorded actions and template test cases.
  • See which steps have no matching action, record the missing controls and check again.
  • Create requirements, linked test cases and, if you tick it, a pipeline in one click.

How to use it

  1. In Analyze, select the module folder (not Documents).
  2. On Import, add the files, set Target scope and click Analyze with AI.
  3. On Requirements & Scenarios, edit the outline and click Generate steps (n).
  4. Click Continue to review (n) and use Check Coverage for the uncovered steps.
  5. On Review & Create, click Create.

The short answer#

When you select a folder in Analyze, the screen becomes a three-step wizard with the tabs Import, Requirements & Scenarios and Review & Create. You attach the document, the AI reads it and proposes an outline: requirement › sub-requirement › scenario. You edit the outline, let the AI write the steps, and click Create.

The result is main requirements with their sub-requirements in the folder you selected, and test cases in that module’s folder in Automate, each linked to its sub-requirement. A step that matches one of your recorded actions uses it. The outline lives on your screen until you click Save as Draft or Create.

The problem this solves#

A requirements document often arrives as a Word or PDF file. A tester reads it, writes test cases into a spreadsheet or a test management tool, and someone automates part of them later. The link between a sentence in the document and a test is kept by hand, if it is kept at all. When the document changes, it is hard to say which tests are affected.

Some teams paste the document into a general chat assistant. That gives a list of test ideas, but the assistant does not know the application’s pages and controls, so the steps have to be written again in the test tool. What is missing is a path from the document to test cases that are linked to their requirement and built on the controls the team has already recorded.

An example#

This is an illustration, not a customer story. A team tests an insurance claim form, and the QA lead receives the specification of the module Claims as a Word file.

  1. In Analyze the QA lead selects the module folder Claims. On Import they add the .docx file, set Target scope to the module, leave Coverage Depth on Standard and click Analyze with AI.
  2. The message reads “Outline ready: 3 requirement(s), 12 scenario(s) — review and edit before generating steps” and tab 2 opens. No steps exist yet.
  3. The QA lead renames one sub-requirement, unticks two scenarios and clicks Generate steps (10). The result: “Steps generated for 10 scenario(s)”. Each scenario now shows a coverage percentage.
  4. On Review & Create most steps are marked ✓. Three steps of the upload dialog are marked ✗, because no action matches them yet. The QA lead clicks Record Actions, records those controls and clicks Check Coverage: “Coverage check completed!”.
  5. The button reads Create (3 req, 10 TC). One click: “3 requirements and 10 test cases created successfully!”.
  6. The test cases are in the module’s folder in Automate, each linked to its sub-requirement. The team opens them there to run and refine them.

The team did not start from an empty sheet: it reviewed an outline, and the test cases it kept are linked to their requirements from the first day.

By hand in a spreadsheet, with a general chat assistant, and with SmartestQA#

QuestionBy hand in a spreadsheetA general chat assistantSmartestQA
Who reads the document?A tester, who also notices what the document leaves outThe assistant, from what you paste or attachThe AI, from the files you add on Import
Can I change the structure before steps are written?Yes, it is your sheetYes, by asking againYes: you edit the outline on tab 2, and steps are written only for the scenarios you keep
Do the steps know my application?As far as the tester knows itNo, unless you describe itA step that matches one of your recorded actions uses it
How do I see what cannot be automated yet?You find out when you automateYou find out when you automateSteps without a matching action are marked ✗, and Check Coverage matches every step again
Is each test linked to its requirement?If you keep a column for itNoEach test case is linked to its sub-requirement
Where does the result live?In the sheet, to be copied into a test toolIn the chat, to be copiedRequirements in Analyze, test cases in Automate
Is the result ready to run?After someone automates itAfter someone automates itYou open the test cases in Automate to run and refine them

Steps#

  1. Check that AI is on

    Analyze with AI needs Enable AI and AI Document Analysis in Project Panel › AI Options; otherwise its tooltip says which one to enable. Only an Admin can open Project Panel. See Turn on AI.

  2. Select the module folder

    In the requirement tree, click the module (a folder marked M) or a sub folder inside it. Requirements are created in the folder you selected. The Documents folder has no wizard. The line AI generation reads: shows what the AI will get from Discover: App Map pages and active Notes. See Before you start.

  3. Add the files and set the scope

    On Import, drop files on the box or use Add files; paste screenshots with Ctrl/Cmd+V. Set Target scope to Whole project, one module or one page. With a module or page, the actions, App Map metadata and screenshots of its pages are sent. See Set Target scope.

  4. Set preferences and click Analyze with AI

    Choose Coverage Depth, Negative Test Intensity, Default Priority and Requirement Type, tick what to generate under Select Entities to Generate, and add a line in Additional Instructions for AI if you want. Click Analyze with AI. The browser waits up to 3 minutes.

    “Outline ready: n requirement(s), m scenario(s) — review and edit before generating steps”, and tab 2 opens.

  5. Edit the outline

    No steps exist yet; each scenario shows the chip outline. Use the pencil to rename, Add sub-requirement, Add scenario and Delete sub-requirement to change the structure, and untick what you do not want. See Requirements & Scenarios.

  6. Generate steps

    Click Generate steps (n) for the selected scenarios. The browser waits up to 10 minutes. A scenario without steps shows failed; keep it selected and click Generate steps again. Then click Continue to review (n).

    “Steps generated for n scenario(s)”. Each scenario now shows a coverage percentage instead of outline.

  7. Fix uncovered steps

    On Review & Create, a step marked ✓ uses an existing action or another test case; a step marked ✗ has no matching action yet. In a web project, click Record Actions, record the controls the ✗ steps need, then click Check Coverage. See Fix uncovered steps.

    “Coverage check completed!”

  8. Create

    The button reads Create (x req, y TC). Click it. Then open the test cases in Automate to run and refine them. See Create.

    “n requirements and m test cases created successfully!” The outline becomes read-only.

Files and preferences#

ItemOptionsNotes
Documents.docx, .doc, .pdf, .txt, .md, .markdown, .html, .htm, .json, .csv, .tsv, .yaml, .yml, .xml, .xlsx, .xlsPDFs must contain text; a scanned PDF has none. Add it as screenshots instead.
Images.png, .jpg, .jpeg, .gif, .webp, .bmp, .svgSent to models that can read images.
Coverage DepthMinimal · Standard · ComprehensiveMinimal asks for the critical paths only, Comprehensive for full coverage. Default Standard.
Negative Test IntensityLow · Medium · HighHow many error, invalid-input and edge-case scenarios to add. Default Medium.
Default PriorityLow · Medium · HighPassed to the AI as the default priority. Default Medium.
Requirement TypeFunctional · Non-Functional · BothWhich kind of requirements to derive.
Select Entities to GenerateRequirement, Sub-Requirement, Test Case, Test Step, PipelineRequirement is always on. Pipeline needs Test Case and is off by default.

What Create makes, and where#

ItemWhereDetails
Main requirementsThe folder you selected in AnalyzeOne tree row each
Sub-requirementsInside their main requirementNo tree rows
Test casesThe Automate twin of the folderLinked to their sub-requirement, in order
StepsIn the test casesA step that matches an action uses it; a step that matches none gets a new action
Template test casesAutomateA run of 3 or more steps that appears in 2 or more selected scenarios becomes a shared template, and the scenarios call it
Test suite and pipelineScheduleOnly with Pipeline ticked. The pipeline runs on the SmartestQA server and needs a Start Page URL; without one only the suite is created

The limits of this step, such as 4 scenarios per batch and 420 seconds of server time for one step generation, are in Limits of this step.

Watch it#

The video shows the hand-made side of Analyze: the requirement tree with one folder per module, writing a main requirement and its sub-requirements, and linking existing test cases to a sub-requirement. It does not show the AI wizard described above.

Video transcript

The tree starts at the project and has one folder per module, marked M, with a count. Open a module and select a main requirement. Its details open beside the tree: status, severity, dates, linked test cases and comments. Assessment (AI) is the next tab. Further down are the documents: specs and notes that AI generation reads. More adds a folder or a new document. Filter By Tags narrows the tree. Archive holds what you removed, until you restore it. New Requirement adds an empty requirement to the tree and opens it. Name it after what the user can do. In Description, say who it is for and what they get. Add opens a sub-requirement: one rule, written so that it can be tested. Add one for each rule, including what must not happen. Generate proposes sub-requirements with AI from the name and description. Save. The requirement takes its name in the tree, with its sub-requirements listed. A sub-requirement is one rule. Select it to see its details on the right. Test Cases lists what proves this rule. Nothing is linked yet. Add opens the test cases of the project. Add the cases that check this rule: here, two tests of the reset form. They now show under the sub-requirement, and their results count for it.

Keep requirements in a tree, write one, and link the tests that prove it.

What you get#

  • An outline you control. Requirements, sub-requirements and scenarios are proposed first; steps are written only for the scenarios you keep.
  • Steps tied to your application. The AI receives your actions as a page graph, your template test cases, your active Notes and the App Map descriptions of the scope, plus up to 6 page screenshots when a scope is set.
  • Fewer duplicates. Up to 10 existing requirements similar to the document are sent, so the AI does not create them again.
  • A coverage figure per scenario. The chip Coverage: n% sums up how many steps use an existing action.
  • Traceability from the start. Each test case is linked to its sub-requirement, which is where SmartestQA counts coverage.
  • Shared templates. Repeated runs of 3 or more steps become one template named [Auto] step → step → ….
  • A draft. Save as Draft keeps the outline with the folder, so you can come back to it.

Questions and answers#

Which file types can I upload, and how big can the document be?Customers

Word, PDF with text, text, Markdown, HTML, JSON, CSV, YAML, XML, Excel and common image formats, several at once. There is no fixed document size, but the browser waits at most 3 minutes for the outline, so split long documents by chapter or module. See Which files can I import?

Can I generate test cases before I have recorded my application?Customers

Yes. With nothing in Discover the wizard says “No application metadata yet — no page map, no notes. Scenarios will be generated from the document alone.” Steps that match no action are marked ✗ and get a new action on Create. See What the AI receives.

Does it work with a scanned PDF or with screenshots?Customers

A scanned PDF has no text, so the wizard cannot read it as a document. Add its pages as screenshots instead: the Import tab accepts images and pasted screenshots, and sends them to models that can read images. See Import.

Can I review and change what the AI proposes before it is saved?Customers

Yes. The outline lives on your screen until you click Save as Draft or Create. On tab 2 you rename, add and delete sub-requirements and scenarios and untick what you do not want; on tab 3 you read every step. See Drafts and what is kept.

What happens when a generated step has no matching control?Customers

The step is marked ✗ on Review & Create and lowers the scenario’s coverage. Record the missing controls with Record Actions and click Check Coverage, which matches every step again. If you create anyway, the step gets a new action. See how coverage is counted.

Can the wizard also create a pipeline to run the new tests?Customers

Yes, when you tick Pipeline under Select Entities to Generate; it is off by default. SmartestQA then creates a suite with all new test cases and a pipeline named AI Generated Pipeline - YYYY-MM-DD in Schedule. See What gets created.

I already have a requirement. Can I generate test cases only for it?Customers

Yes. On a saved sub-requirement whose description has at least 10 characters, click Automate, then Analyze. The AI proposes 1 to 3 end-to-end test cases; tick the ones you want and click Create. This quick path has no Check Coverage. See Generate test cases for one sub-requirement.

Is my document sent to an AI provider?Customers

Yes. The attached documents and images, the actions and App Map descriptions of the scope, template test cases, similar existing requirements and active Notes go to the AI provider configured for the project. Use documents without personal or customer data. See What does Analyze send to the AI provider?

Can I import requirements from Jira or Confluence?Customers

Analyze has no Jira import. You can export the issues to a file and use the AI wizard, or let an AI assistant write them through MCP. From Confluence, an import works only through an AI assistant connected through MCP. See Can I import requirements from Jira or Confluence?

Does it work for mobile and desktop projects?Customers

Yes, the same way. Two parts of the wizard assume a web app: Record Actions uses the browser extension, and the optional pipeline needs a Start Page URL. For mobile and desktop, capture missing controls in Discover and create pipelines in Schedule. See Does Analyze work for mobile and desktop projects?

Read more#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai