Rover provides a convenient way to copy your Execution Sets and Incidents to your client machine or device to enable offline testing.
To synchronize your Execution Sets and Incidents you will need an internet connection or be able to access your ET Server if your ET site is not accessible through the internet. This may mean that you need to be connected to your office network for the download and upload processes.
Downloading Entities
Downloads are performed on the entity (Execution Sets and Incidents) screen. If you are planning to download both script assignments and incidents, then you will need to navigate to each tab and and select the entities you wish to download to your local machine or device.
In Rover, you can select the drop down next to the project name to display all available projects (this depends on your permission settings on the ET Server).
Once the project is selected, select the tab for the entity you wish to download. The green play tab represents Execution Sets/Test Runs and the orange bug tab represents Incidents.
Execution Sets/Test Runs
Incidents
To download entities, click on the download icon next to the folder or the individual entity you wish to select.
You can also select all folders and entities for download but clicking on the top level folder.
Once you have downloaded your entities, the download icon will disappear.
Uploading Entities to the ET Server
Once you have completed your testing, you can upload your runs and incidents back to the ET server by navigating to the Sync tab.
The Sync Dashboard will provide you with a list of all entities, both script assignments and incidents, that have been downloaded from the ET Server or created locally across all projects. you can easily select the entities you wish to sync back to the ET Server.
You can select the top level folder to select all entities under the folder or select the Hide Synced option to only show entities that have changed since the last synchronization and select only those entities.
You may notice a yellow warning icon appears when you you have selected some of the script assignments. This warning indicates that the run may not be complete. If you proceed with the sync, the run will automatically completed and you will not be able to resume the run. You may wish to deselect these entities before proceeding.
When you are ready to sync, select Sync Selected. This will initiate synchronization with the ET server. Once you have completed your synchronization only failed and entities that were deselected from the sync will be shown.
If a failed icon appears, hover the mouse or press & hold your finger on the icon to view the message. In some cases, you may need to try re-syncing. If you receive the error: "This item has been deleted from the server and cannot be synchronized, it can only be purged", then this means that the script assignment in the execution set in your ET project has been deleted and Rover cannot map this entity back to the server. The only option is to delete the entity. Before you delete the entity you can review it for data that you don't wish to lose.
Once you have completed synchronizing your results, you may wish to clean up your local database by deleting the entities stored locally. You can do this by again selecting the entities and then clicking or tapping the Purge Selected button.
Notes on Synchronization
Synchronization requires matching of the ET ID for each entity to successfully synchronize entities between Rover and the ET server. Some changes made to the ET Server between downloading to Rover and uploading results and updated from Rover may cause synchronization issues. Below are some causes of synchronization failure:
- Deletions on the ET Server - If script assignments are deleted from the the ET Server, any runs or updates that have been created will not sync back to ET even if you re-create the script assignment. As Rover uses the ET ID to map entities back to the ET server, on deletion this ID will no longer exist and therefore cannot be mapped.
- Baseline restore in ET - Baselines restores in ET should not be performed if you are also executing tests using Rover. Although a baseline restore does restore a project to a previous state, the IDs are not the same and will be replaced with new identifiers. Entities will not be able to synchronize back to ET if a baseline restore is preformed between the download and upload of entities. Caution should be taken when considering a baseline restore.
- Custom field configuration - If custom field are made mandatory or new mandatory custom field are created and scoped to your project between synchronization of entities with Rover, this will cause the synchronization to fail as the mandatory requirements for saving have not been met. In this case you will need to make the the field not required then initiate your synchronization.
Troubleshooting Synchronization
If you are having trouble diagnosing the cause of your synchronization failure, please send send a copy of your Rover log file for the day that your sync failed to the Catch Support Team. The Log files can be found with your Rover installation files.e.g. C:\Program Files (x86)\ET+Rover+1.0.000\Log. Please also note the time of the failure.