Documentation Index
Fetch the complete documentation index at: https://docs.testfactors.com/llms.txt
Use this file to discover all available pages before exploring further.
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.
What this module does
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 position Test 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.
Who uses this module
| Role | Generate | Approve / Promote | Edit | Reject |
|---|---|---|---|---|
| Test Manager / Project Manager | Yes | Yes | Yes | Yes |
| Test Coordinator / Module Process Owner | Yes | Yes | Yes | Yes |
| Tester | Yes (own) | No | Limited | Yes |
| Developer | Yes (own) | No | Yes | Yes |
| Viewer | No | No | No | No |
Before you start
You need:- At least one approved scenario in this project. See Scenarios & Categories.
- A test cycle selected. Test cases are generated per cycle, just like scenarios.
Step-by-step: generate and review test cases
Open a scenario
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).
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…”
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)
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?”).
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
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.
Refining proposals with chat
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”
Editing a test case
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
Tips
Approve in waves
Approve the obvious 70% first, then come back to edge cases. Reviewing the easy ones fast frees mental energy for the hard ones.
Use bulk approve aggressively
If the first 5 proposals are good, the next 10 from the same batch usually are too. Trust the pattern.
Reject with one-line reasons
“Wrong job code — we don’t use Engineering” is gold for AI training. “Bad” is not. Specifics make the next batch noticeably better.
Edit, don't reject + recreate
If 90% of a proposal is right and 10% is wrong, edit. Rejecting and asking the AI to re-propose costs you tokens and re-review time.
Group related cases
Test cases inherit from their scenario, which inherits from a category. Keep this hierarchy clean and your test runs will be much easier to navigate.
Don't manually write what AI can draft
Even if you “know” what the test cases should be, generate first. The AI catches edge cases you’d skip when typing them by hand.
Test case states
| State | Meaning | Can be executed? |
|---|---|---|
| Proposed | AI drafted, awaiting human review | No |
| Active | Approved, in the live test library | Yes |
| Edited | Modified after approval | Yes |
| Archived | Removed from active use but kept for history | No |
| Rejected | Proposal was rejected; reason kept for AI training | No |
Troubleshooting
The AI proposed identical-looking test cases
The AI proposed identical-looking test cases
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
The Approve button is missing
Generated test data has placeholder values like 'TBD' or 'XXX'
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
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)
Generation never finishes (banner stuck)
I edited a test case but the changes aren't reflected in the test script
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.
Related guides
Scenarios & Categories
Test cases live inside scenarios — start there if you haven’t generated scenarios yet.
Test Scripts
Next step: turn approved test cases into step-by-step scripts.
Workbooks
Test data comes from your workbook — keep it clean and the AI generates better cases.
Knowledge Wiki
Add domain rules so the AI uses your real test data, not placeholders.