Synchronization – Rover Plugin

Synchronize ‘Execution Sets’ and ‘Incidents’ in Rover. A convenient way to copy ‘Execution Sets’ and ‘Incidents’ to a client machine or device to enable offline testing.

Synchronizing ‘Execution Sets’ and ‘Incidents’ requires ET Server access either directly or through the internet. This may require a network connection to your office for the download and upload processes.

Synchronize ‘Execution Sets’ and ‘Incidents’: Downloading Entities

Perform downloads from the ‘Entity’ (Execution Sets and Incidents) screen. To download script assignments and incidents, navigate to each tab and select the entities for your local machine or device.

To display all projects in Rover select the drop down next to the project name. Available projects depend on permission settings from the ET Server.

Select the project then the tab for the entity 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.  

Select all folders and entities for download but clicking on the top level folder.

The download icon will disappear when entities are downloaded.

Synchronize ‘Execution Sets’ and ‘Incidents’: Uploading Entities to the ET Server

To upload runs and incidents back to the ET server navigate to the ‘Sync’ tab after testing is complete.

The ‘Sync Dashboard’ will provide you with a list of all entities downloaded or created locally across all projects. Easily select the entities (script assignments or incidents) to sync back to the ET Server.

Select the top level folder to select all entities under the folder. Select the ‘Hide Synced’ option to only show entities that have changed since the last synchronization for selection.

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. Proceeding with the sync will automatically complete the run and cannot be resumed.  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. Only failed and deselected entities from the sync are shown once synchronization is complete.

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. The error “This item has been deleted from the server and cannot be synchronized, it can only be purged”; indicates the ET project execution set’s script assignment has been deleted and Rover cannot map the 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, deleting the entities stored locally cleans up your local database. 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. Changes made to the ET Server between downloading to Rover and uploading results or updates may cause synchronization issues. Below are some causes of synchronization failure:

• Deletions on the ET Server – Script assignments deleted from the the ET Server will not sync back to ET. Even if you re-create the script assignment, any runs or updates that have been created will not sync. Rover maps entities to the server using ET IDs, which therefore cannot be mapped upon deletion.
• ‘Baseline Restore’ in ET – ‘Baseline Restore’ in ET should not be performed if you are also executing tests using Rover. When restoring projects to a previous state new identifiers replace IDs. A ‘Baseline Restore’ performed between download and upload disrupts entities synchronizing to ET Server. Take caution when considering a baseline restore.
• Custom Field configuration – Synchronization fails when mandatory Custom Field requirements are not met. New or altered mandatory fields scoped to the project between synchronization of entities must be made not mandatory when initiating synchronization.

Troubleshooting Synchronization

For assistance diagnosing a synchronization fail, send the day’s Rover log file 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.