Our documentation site has been updated to AIO Tests Knowledge Base
Execute Cycle Offline
- Noopur Varshney [AIO Tests]
In order to further enhance the cycle execution usability for users, AIO Tests now offers bulk update step results and other artifacts of execution results through Excel. This not only adds another view to the cycle execution results but will also help users transitioning 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. This article shows how to use Execute Offline feature in AIO Tests.
Offline execution for a cycle can be initiated from the Cycle Details page as shown below and it is a 2-step process (export and then import). The sections below discuss the 2 step process in detail.
Click ‘Execute Offline’ from the top-right ellipsis of the Cycle details page.
Export Cycle Run Data
The first step is to export the existing cases and runs data from AIO Tests as an excel by selecting the ‘Export Cycle Run Data’ option.
Once you click on Confirm, an Excel Download begins. Below is a sample Cycle export excel 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 Run row would be added as single comment to run |
| Text in Step row would be added as single comment to step |
Run Defects/Step Defects | Comma separated values of defect keys from Jira |
| Existing defects, if removed, will be removed from 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 on import |
Actual Result | Actual result specified would be added to actual result of 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 file being imported, case will not be removed from cycle. |
| If a step is removed from a case run in file being imported, no changes will be made to step in the run on import. |
Import Offline Execution Results
Once you are done updating the excel, the next step is to import the excel into AIO Tests. Go to the cycle from which export was taken and click on Execute Offline again.
This time choose ‘Import Offline execution results’ radio button to get the screen shown below.
Attach the updated excel using “browse to upload file” option. If you want to record the results from excel as a new run, click the checkbox in the modal and then click Confirm. If new run check-box is selected, all the updates from Excel will be recorded for the newly created run. Users will get a success modal like the one shown below.
Key points
While importing actual effort, the decimals are ignored if specified. e.g. 57.6 minutes will be imported as 57 minutes
The status is captured at level it is specified. It doesn’t percolate down or up. e.g. all steps are marked as Passed in Step Status column and no update is made in the Run Status column, then Run Status will stay as in (marking steps as passed won’t automatically percolate up to run being marked as Passed)
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 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 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 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 cycle. Please export 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>. 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 positive value for effort | Actual effort provided is a negative value | Fix the value and reimport to same run |
Warning: Actual effort not updated. Please specify effort in minutes | Actual effort is not in correct format (needs to be specified in minutes) | Fix the value and reimport to same run |
Warning: Run/Step defects not found : <not found ids> | Defect ID provided is incorrect | Fix the value and reimport to same run |