Execute Offline
- APPWRK Writer
- Noopur Varshney [AIO Tests]
AIO Tests allows users to bulk update step results and other artifacts of execution results through Excel to enhance the cycle execution usability for users. By executing Cycles offline, you can not only add another view to the cycle execution results but also help users transition from Excel to quickly report results. This feature can also be helpful in distributing cases for execution to testers who do not have access to Jira.
In this documentation, you’ll understand:
Steps to Export Cycle Run Data
Step 1: To export cycle run data, simply click on the Cycles option in the top bar menu.
Step 2: On the Cycles page, right-click on the cycle that you want to execute offline and hit the Execute Offline option from the drop-down menu.
Users can also export cycles offline from the Cycle detail page.
Step 3: Once you click on the Execute Offline option, the Execute Offline modal window will appear on the screen. Tick the Export Cycle Run Data radio button and hit the Confirm button.
Once you click on the Confirm button, an Excel file will be downloaded. Below is a sample Cycle Export Excel file from AIO Tests.
The export has 18 columns, along with an instruction sheet. The below table describes each of them along with possible actions on each column.
Column | Details |
Key, Title, Preconditions | Case details for the exported cases |
| Users should not delete or edit the key, else it will error out on import. Edits done to title and preconditions will not carry over on import |
Run Status/Step Status | Choose from available status options - Not Run, In Progress, Blocked, Passed, Failed |
Existing Run Comment/Step comment | Already added comments are visible. It’s a read-only value |
Run Comment/Step comment | Comment to be added to run/step |
| Text in the Run row would be added as a single comment to run |
| Text in the Step row would be added as a single comment to the step |
Run Defects/Step Defects | Comma-separated values of defect keys from Jira |
| Existing defects, if removed, will be removed from the run/step |
Actual Effort | Actual effort to be logged in minutes |
Order/Steps/Data/Expected Result | Case steps and related details |
| Any changes to details will not carry over to import |
Actual Result | The actual result specified would be added to the actual result of the step |
Run ID | Run ID of each run from AIO Tests |
| Do not change |
Step ID | Step id of each step from AIO Tests |
| Do not change |
General | If a case is removed from the file being imported, the case will not be removed from the cycle. |
| If a step is removed from a case run in the file being imported, no changes will be made to the step in the run on import. |
Steps to Import Offline Execution Results
Step 1: To import offline execution results, all you need to do is click on the Cycles option in the top bar menu.
Step 2: On the Cycles page, right-click on the cycle that you want to import offline and hit the Execute Offline option from the drop-down menu.
Users can also import offline execution from the Cycle detail page.
Step 3: Once you click on the Export Offline option, the Execute Offline modal window will appear on the screen. Tick the Import offline execution results radio button. Click on the Browse to Upload File option to attach the updated Excel file and hit the Confirm button.
If you want to record the results from Excel as a new run, click the checkbox Create new run for results in the modal. If the new run checkbox is selected, all the updates from Excel will be recorded for the newly created run.
Once you click on the Confirm button, a success modal will appear on the screen.
Troubleshooting Errors
There are some standard errors that can be seen for particular situations. The explanation and remedies are listed below:
Displayed Error/Warning | Description | Fix |
Warning: Case key was not found (reported against Run ID) | Case key was changed from the imported Excel | No change is required as all other data will be updated |
Warning: Case key was not found (reported against Row ID) | Case key was deleted/removed from the imported Excel | No change is required as all other data will be updated |
Error: Invalid format for run ID | Run ID provided is incorrect | From AIO Tests, filter the case which failed and export the case run data and reimport |
Error: Step ID(s) not found: <step ID>. Please export the latest run data | Step ID provided is incorrect | From AIO Tests, filter the case which failed and export the case run data and reimport |
Error: New run with a new version of the case has been added to the cycle. Please export the latest run data | After exporting, another user created a new run in AIO Tests using a newer version of the case | From AIO Tests, filter the case which failed and export the case run data and reimport |
Error: Step id not found in case: <step ID>. The referenced case may have changed | After exporting, one of the linked cases has changed | From AIO Tests, filter the case which failed. Add a new run. Then, export the case run data and reimport |
Warning: Actual effort not updated. Please specify the positive value for effort | Actual effort provided is a negative value | Fix the value and reimport to the same run |
Warning: Actual effort not updated. Please specify effort in minutes | Actual effort is not in the correct format (needs to be specified in minutes) | Fix the value and reimport to the same run |
Warning: Run/Step defects not found: <not found ids> | Defect ID provided is incorrect | Fix the value and reimport to the same run |
For further queries and suggestions, feel free to reach out to our customer support service via help@aiotests.com.