Review, edit, and approve AI-drafted test cases in TestFactors — the specific situations within each scenario that your team needs to verify.
Test cases are where ‘what we want to test’ becomes ‘exactly what we’ll verify.’ This is the layer that catches the edge cases that scenarios are too broad to cover.
A scenario is broad (“Hire a US employee into an active position”). A test case is a specific instance of that scenario with concrete data:
Scenario: Hire a US employee into an active positionTest case 1: Hire a salaried US employee, exempt, with stock eligibility, into an existing active position in the Engineering department.Test case 2: Hire an hourly US employee, non-exempt, no stock, into a position requiring background check.Test case 3: Hire a US employee into a position with future-dated start date (Q3 next year).
TestFactors generates test cases from your scenarios using:
Workbook data — every field in your spec that affects the scenario becomes a variable.
Picklist values — every option in a relevant picklist becomes a variant.
Edge case patterns — null values, max-length strings, boundary dates, special characters.
Your knowledge wiki — any custom rules or constraints you’ve documented.
You stay in control: every AI-generated test case sits in a Proposed state until you approve, edit, or reject it.
Testers can propose test cases and reject AI output, but only Test Coordinator+ can promote a proposed test case to active. This keeps the active test library curated.
From the Scenarios tab, click any active scenario. You land on the Scenario detail view with a list of its test cases (empty on first open).
Scenario detail page with an empty test cases section and a 'Generate Test Cases' call-to-action.
2
Click Generate Test Cases
Click the primary Generate Test Cases button. The AI starts analyzing the scenario plus the underlying workbook data.A progress banner appears: “AI is drafting test cases…”
Generation in progress with progress banner and the first few proposed test cases starting to appear.
3
Wait for proposals
Generation usually takes 15–30 seconds depending on scenario complexity. You’ll see between 3 and 25 proposed test cases per scenario.Each proposal arrives with:
A clear title (“Hire salaried exempt US employee with stock”)
Preconditions (“Position must be Active, requisition approved”)
Test steps (numbered actions)
Expected results (one per step)
Test data (the specific values to use)
Test cases list showing 12 proposed cases in 'Proposed' state with a Review badge on each.
4
Open a proposal and review
Click any proposed test case to open the detail panel. You’ll see the full structure: title, description, preconditions, steps with expected results, test data, and AI rationale (“Why did the AI propose this?”).
Test case detail panel with steps, expected results, test data, and AI rationale visible.
5
Approve, edit, or reject
Each proposal has three primary actions in the top-right:
Approve — promotes the proposed test case to Active in your test library
Edit — open inline editor to tweak title, steps, expected results, or test data, then approve
Reject — discards the proposal. Optionally add a one-line reason that trains the AI for next time
Test case action bar showing Approve, Edit, Reject buttons and the 'Approval feedback' field.
Don’t edit unless you must. If the AI’s title or steps are close-enough, approve as-is — you can always refine later. Most teams approve 70–80% of proposals without changes.
6
Bulk approve when you're confident
For tight scenarios with consistent quality proposals, use Bulk Approve: select multiple proposals with the checkboxes and click Approve selected.
Test cases list with 5 checkboxes ticked and the 'Approve selected (5)' bulk action visible.
You’re done. Approved test cases are now in your test library. The next step is generating test scripts — step-by-step instructions a tester can follow. See Test Scripts.
Like every AI surface in TestFactors, test case generation has a chat panel. After the first batch of proposals lands, try:
“Add 3 more negative test cases focused on validation failures”“The data values are too generic — use actual values from our workbook for the Job Code field”“Split the long test case in step 4 into two smaller cases”“Make the test data more realistic — use real-looking US names and SSN-style IDs”
Chat panel open beside the test cases list with a user request and the AI's proposed changes highlighted.
The AI’s revised proposals appear as new “Proposed” rows. Your previously approved test cases are never touched.
Click any test case (proposed or active) to open the detail panel.
2
Click Edit
Top-right of the detail panel. The view becomes inline-editable.
Test case in edit mode with all fields editable inline.
3
Make your changes
Title — change wording
Description — add background
Preconditions — add or remove
Steps — add, reorder (drag-and-drop), delete
Expected results — one per step
Test data — change values, add columns, remove columns
4
Save
Click Save in the top-right. The status stays as it was (Proposed stays Proposed, Active stays Active). Edits are versioned — you can always see what changed in the History tab.
Usually means your scenario is too narrow — there’s only one meaningful way to test it. Two options:
Broaden the scenario — open the scenario, edit the title/description to cover more ground, regenerate
Approve the best one, reject the rest with reason “Duplicate of TC-XXX” — trains the AI not to duplicate next time
The Approve button is missing
Your role doesn’t include test case promotion. Tester role can propose and reject but not approve. Ask your Test Coordinator or Project Manager to approve, or to grant you a higher role.
Generated test data has placeholder values like 'TBD' or 'XXX'
The AI uses placeholders when it can’t infer a concrete value from your workbook. Two fixes:
Edit the placeholder before approving — replace with your actual test data
Add the data to your knowledge wiki — document standard test values for your project so the AI uses them on the next generation
I want to mass-reject everything from one batch and re-generate
Select all checkboxes → Reject selected. Then click Generate Test Cases again. You can pass guidance in the chat: “Don’t focus on validation — generate happy-path cases only this time.”
Generation never finishes (banner stuck)
Typical generation finishes in under 60 seconds. If it’s stuck:
Refresh the page — proposals may already be there
Click Cancel generation (if visible)
Retry; if it stalls again, contact your Admin
I edited a test case but the changes aren't reflected in the test script
Test scripts are generated from test cases at a specific point in time. If you edit the test case after a script was generated, regenerate the script to pick up your changes. See Test Scripts.
