In a newly created sprint branch, automated testing starts with no predefined content. To test and validate content, add test scenarios via forking or creating new ones.Finalize necessary changes to endpoint resources in the APIs section first before organizing test scenarios for automated testing. This aligns with typical development workflows.
Forking Test Scenarios from Main Branch#
The system automatically identifies and selects test scenarios that include endpoints already forked into the sprint branch, making it easier for testers to filter and import them.Automatic folder hierarchy:All parent folders of forked resources are automatically included in the current sprint branch folder. Forked resources display visible association indicators, similar to resources in APIs.Creating New Test Scenarios#
When new endpoints are added to the current sprint, create new test scenarios to validate them:1.
Use the New feature to add test scenarios to the current sprint branch
Designing Test Scenarios#
In forked or newly created test scenarios, you can organize steps similarly to the main branch. The UI clearly indicates whether a test step uses resources from the sprint branch or the main branch.Concentrate on steps impacted by the current sprint branch resources. Fill in new request parameters based on modified endpoint documentation to quickly set up complete test scenarios.Three types of test steps show their association with branch resources:Import from endpoint cases
Reference other test scenario
Running Test Scenarios#
Once test scenarios are created and designed, run them to start the testing process.Sprint branch resources: Uses data from the sprint branch (e.g., modified response data schema for validation)
Main branch resources: Uses data from the main branch
