1. Docs
  2. Build tests
  3. Analyze
  4. Generate from documents with AI

Generate requirements and tests from documents

Select a folder and Analyze becomes a three-step wizard. The AI reads your document, proposes requirements and scenarios, writes steps from your Discover actions, and creates it all when you approve.

7 min read Updated CustomersAdmins

In short

On this page you can

  • Attach DOCX, PDF, text files or screenshots, several at once.
  • Limit the AI to one module or page with Target scope.
  • Edit the proposed requirements and scenarios before any step is written.
  • Generate steps, then check which steps match existing actions with Check Coverage.
  • Create requirements, test cases and optionally a pipeline in one click.

How to use it

  1. Select a module folder; on Import, add files and set Target scope.
  2. Choose preferences and entities, then click Analyze with AI.
  3. On Requirements & Scenarios, edit the outline and click Generate steps.
  4. Click Continue to review, fix ✗ steps with Record Actions and Check Coverage.
  5. On Review & Create, click Create.

The wizard appears when you select a folder in the tree (not Documents). Its tabs are Import, Requirements & Scenarios and Review & Create. Tabs 2 and 3 open once an outline exists; their badges count scenarios (see Wizard counts).

Before you start#

  • 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.
  • The right folder is selected. Requirements are created in the folder you selected, and test cases in that module’s folder in Automate. Select the module, or a sub folder inside it.
  • Discover knows the app. The line AI generation reads: shows what the AI will get: App Map pages (and how many are verified) and active Notes. With nothing there you see “No application metadata yet — no page map, no notes. Scenarios will be generated from the document alone.” Metadata takes you to Discover.

1. Import#

Import tab with two files attached, Target scope set to a module, AI Analysis Preferences, Select Entities to Generate and the Analyze with AI button
The Import tab.
  1. Add files

    Drop files on the box, click it (Click to select a file) or use Add files. Paste screenshots with Ctrl/Cmd+V: “n screenshot(s) pasted from clipboard”. The box shows “n file(s) attached”. A file with the same name, size and date is skipped.

  2. Set Target scope

    Pick Whole project, one module or one page. With a module or page, “The actions, App Map metadata and screenshots of n page(s) are sent.” Without one, “No scope: matching actions are chosen by similarity to the document.”

  3. Set preferences

    Under AI Analysis Preferences, see the table below.

  4. Choose what to generate

    Under Select Entities to Generate, tick what you want. Requirement is always on; the others depend on each other (see Entities).

  5. Add instructions (optional)

    In Additional Instructions for AI, for example “Focus on login and payment flows; ignore the admin chapter.”

  6. Click Analyze with AI

    The status moves from “Reading document...” to “Building the requirement outline...”. 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.

Accepted files: .docx, .doc, .pdf, .txt, .md, .markdown, .html, .htm, .json, .csv, .tsv, .yaml, .yml, .xml, .xlsx, .xls, and images .png, .jpg, .jpeg, .gif, .webp, .bmp, .svg. PDFs must contain text; a scanned PDF has none (add it as screenshots instead).

Save without AI: Create as Document stores the first attached file in the Documents folder and runs no analysis.

AI Analysis Preferences#

PreferenceOptionsEffect
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 Generate#

EntityRule
RequirementAlways on.
Sub-RequirementTurning it off also turns off Test Case, Test Step and Pipeline.
Test CaseNeeds Sub-Requirement. Turning it off also turns off Test Step and Pipeline.
Test StepTurning it on also turns on Test Case and Sub-Requirement.
PipelineNeeds Test Case. Off by default. See what gets created.

What the AI receives#

  • The text of every attached document, and the images, for models that can read images.
  • Your actions as a page graph: those of the scope pages, or ones chosen by similarity to the document.
  • Your template test cases, so steps can reuse them.
  • Up to 10 existing requirements similar to the document, so it does not create duplicates.
  • Your active Notes and the App Map descriptions of the scope, plus up to 6 page screenshots when a scope is set.

Your document goes to the AI provider

Everything above is sent to the AI provider configured for the project. Use documents without personal or customer data.

2. Requirements & Scenarios#

The outline is a tree: requirement › sub-requirement › scenario. No steps exist yet; each scenario shows the chip outline. Everything is selected at first.

  1. Edit the outline

    Use the pencil to rename requirements, sub-requirements and scenarios. Add sub-requirement, Add scenario and Delete sub-requirement change the structure. Untick what you do not want.

  2. Generate steps

    Click Generate steps (n) for the selected scenarios. The browser waits up to 10 minutes.

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

  3. Retry failures

    A scenario without steps shows failed and “Step generation failed for this scenario. You can try again.” Keep it selected and click Generate steps again; scenarios that already have steps are skipped.

  4. Continue

    Click Continue to review (n). It needs at least one selected scenario with steps.

Also on this tab: Check Coverage, Record Actions and Save as Draft (see Fix uncovered steps and Drafts). Cancel discards the outline.

3. Review & Create#

Each scenario lists its steps. A step marked ✓ uses an existing action (its name and type are shown) or another test case; a step marked ✗ has no matching action yet. The chip Coverage: n% and the bar sum this up; see how coverage is counted.

Fix uncovered steps#

  1. Record the missing actions (web)

    Click Record Actions, pick the Start Page URL and Environment (DEV, TEST or PRP Environment) and start. “Recording started! Create actions in the new tab.” Record the controls the ✗ steps need, as in Record Actions.

  2. Check Coverage

    Back here, click Check Coverage. Every step is matched again against your current actions: “Coverage check completed!”.

Create#

  1. Review the selection

    The button reads Create (x req, y TC), with + Pipeline when you chose Pipeline on Import. Selected scenarios must have steps; otherwise saving is blocked with “n selected scenario(s) have no steps yet…”.

  2. Click Create

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

Back to scenarios returns to tab 2 without losing anything.

What gets created#

ItemWhereDetails
Main requirementsThe folder you selected in AnalyzeOne tree row each
Sub-requirementsInside their main requirementNo tree rows
Test casesThe Automate twin of the folder: the module’s folder, or a sub folder with the same name inside itLinked 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 named [Auto] step → step → …, and the scenarios call it
Test suite and pipelineScheduleOnly with Pipeline ticked: a suite with all new test cases and a pipeline named AI Generated Pipeline - YYYY-MM-DD that runs on the SmartestQA server. It needs a Start Page URL (the default one, else the first); without one only the suite is created.

Next: open the test cases in Automate to run and refine them, then check the requirement with Assessment (AI).

Drafts and what is kept#

  • The outline lives on your screen until you click Save as Draft or Create. Save a draft before you switch folders or leave the page.
  • A folder remembers its draft, its preferences and the first file you attached. Attachments beyond the first and the Target scope are not kept.
  • After Create the draft is read-only. Start a new analysis for more.
  • A folder with requirements but no draft opens on tab 2 with its main requirements listed read-only.

Limits of this step#

ItemLimit
Browser wait for the outline3 minutes
Browser wait for step generation10 minutes
Server time for one step generation420 seconds, in batches of 4 scenarios, 4 batches at a time
Step generations running at once on the server3 (others wait up to 60 seconds for a slot)
App Map screenshots with a scope6
Similar existing requirements sent10

If something goes wrong#

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

info@smartestqa.ai