Levels of Recovery Configuration
Recovery Steps can be defined at three levels in Avo Assure:
Priority
Level
Description
1
Test Case-Level
Executes recovery only for that test case
2
Sub-Folder-Level
Executes recovery for that sub-folder
3
Folder-Level
Executes recovery for the entire folder
This hierarchy ensures the appropriate recovery mechanism is applied based on scope.
Folder-Level Recovery Steps
Applies to all test cases within a folder, including sub-folders. suitable for common dependencies across multiple test cases.
Example: Restart the application if any test case fails.
Sub-Folder-Level Recovery Steps
Applies to test cases within a specific sub-folder only. Overrides folder-level steps for those test cases.
Example: Clean up data specific to a module.
Test Case-Level Recovery Steps
Applies only to the selected test case. Ideal for unique or custom recovery logic.
Example: Clear a corrupted download file before re-running a specific test.
Use Case Example: Banking Tests
Banking Tests (Folder)
│
├── Login Tests (Sub-folder)
│ ├── TC01 - Valid Login
│ └── TC02 - Invalid Login
│
├── Fund Transfer Tests (Sub-folder)
│ ├── TC03 - Transfer to Own Account
│ ├── TC04 - Transfer to Third-party Account
│ └── TC05 - Add New Beneficiary
│
├── Statement Tests (Sub-folder)
│ └── TC06 - Download Account Statement
1. Folder-Level Recovery Steps: Banking Tests
Applies To: All test cases
Scenario: Banking app crashes or becomes unresponsive.
Steps:
Close all browser sessions
Restart the banking application
Re-login with default credentials
Purpose: Resets the environment for any test case to re-run smoothly.
2. Sub-Folder-Level Recovery Steps: Fund Transfer Tests
Applies To: Test cases in “Fund Transfer Tests” only
Scenario: Test fails due to leftover data or duplicates.
Steps:
Delete unapproved beneficiary entries
Reset transfer limits
Clear fund-transfer session cookies
Purpose: Prevents re-execution failures due to data conflicts.
3. Test Case-Level Recovery Steps: TC06 - Download Account Statement
Applies To: TC06 only
Scenario: Incomplete or corrupted PDF download affects next run.
Steps:
Delete partial/corrupted PDFs from Downloads
Restart browser to reset session
Purpose: Ensures clean execution for the next test run.
Recovery Step Execution Priority
When recovery steps exist at multiple levels, only the most specific is executed:
Priority
Level
Applied To
Example
1
Test Case-Level
TC06 only
Delete failed downloads, restart browser
2
Sub-Folder-Level
Fund Transfer test cases
Clear data, reset limits
3
Folder-Level
All test cases
Restart browser and app
Last updated
Was this helpful?