Prepare Test Cases
Test Scopes allow you to generate, review, and organize test cases for the feature or module being tested. Test cases can be generated automatically from uploaded source files or added from the Test Case Library.
Generate Test Cases
If source files are available in the scope, TestFirst can analyze them to generate draft test cases.
You can generate test cases:
during initial scope creation
anytime from Sources → Generate test cases
What Happens During Generation
TestFirst analyzes uploaded source files and extracts:
functional requirements
expected behaviors
user flows
constraints and edge cases
From this analysis, the system produces:
coverage of the feature behavior
a draft hierarchy of suites, sections, and test cases
This structure provides an initial testing framework that can be reviewed before being added to the scope.
Handling Low-Quality Inputs
The quality of generated tests depends on the quality of the uploaded files.
Possible outcomes:
If all files contain little useful information, generation may produce minimal output or display a warning.
If at least one file contains useful information, meaningful test scenarios can still be generated.
Duplicate tests with the same name and folder are removed automatically.
Review Generated Test Cases
After generation, a review screen appears where you select the tests that should be added to the scope.
The review interface contains two panels:
Left panel
Displays generated test cases
Right panel
Shows tests selected for the scope
Generated items may include:
NEW – AI-generated test cases
EXISTING – tests already available in the Test Case Library
Select Test Cases
During review you can:
select or deselect individual tests
select all tests within a folder
expand or collapse the test hierarchy
Once confirmed, selected tests are automatically added to the Test Scope.
Add Test Cases from the Library
Existing tests can also be added from the Test Case Library.
To add tests from the library:
Open the Test Scope Detail Page
Click + Add From Library
Browse the library hierarchy
Select the tests to include
The library browser displays:
full test hierarchy (suites, sections, subsections, test cases)
test status (Draft / Ready for testing)
Items that are already present in the scope are automatically filtered out.
Selected items appear in the Test Cases Tree.
Manage Test Cases in the Scope
All tests added to the scope appear in the Test Cases Tree. From this tree you can organize and manage tests within the scope.
Remove From Scope
This action:
removes the test from the current scope
does not delete the test from the Test Case Library
This is useful when a test should not be included in this scope but may still be used elsewhere.
Remove Permanently
This action deletes the test globally.
Key rules:
requires Test Case Delete permission
removes the test from the Test Case Library
affects all scopes referencing the test
Folder Deletion Rules
A folder cannot be deleted if:
some child tests exist elsewhere in the library
some tests are not visible within the current scope
This prevents accidental deletion of shared test structures.
Complete Draft Test Cases
Before tests can be executed, each draft test case must be completed. Completing a test case means defining the steps that verify the expected behavior of the system.
A test case can be completed in two ways: by automating it using the Recorder or by defining the steps manually in the Test Case Editor.
Automate the Test Case using the Recorder
Test cases can be automated using the Recorder, a tool available inside the TestFirst Editor which captures browser interactions and converts them into automated test steps.
These recorded steps become part of the test case and can later be edited, extended, or combined with manually written steps. This approach is commonly used for UI test automation and allows tests to be created without writing code.
Write Test Steps Manually
Test cases can also be completed manually using the TestFirst Editor.
In the editor you can define:
Preconditions
Test steps
Expected results
Manual completion is useful for tests that cannot be automated using recorder.
Once a test case is completed, it can be marked as Ready for testing and included in test execution.
Last updated