Rover provides you with the ability to run tests from Enterprise Tester when you are on the go - working in remote locations, or in areas where internet connectivity is unreliable or unavailable.
Rover supports synchronizing both script assignments and incidents with Enterprise Tester. This article covers synchronizing and running script assignments.
Although internet access is not required to run tests in Rover, internet access is required:
- When downloading script assignments and incidents from the ET server.
- When uploading test run results, new incidents and new comments on existing incidents to the ET server.
The Getting Started article provides an introduction to help users become familiarized with Rover.
Copying Scripts and Execution Sets to Rover
An internet connection is required for this task.
After logging into Rover, the navigator will display the execution set folders and their script assignments (but not their agile runs) in the first project listed in the Enterprise Tester navigator.
In Enterprise Tester:
In Rover, the execution icon is highlighted in green and the contents of the default project is displayed:
You can change the project by selecting from the drop down list. Projects are organised into categories, just like in ET. Users will only be able to see projects that are defined in their user permissions on the ET server.
Once the project is selected, you can then review and select the execution sets you wish to download from the ET server.
To download execution sets, click on the folder or the individual script assignment you wish to select. You can also download all execution sets and script assignments by clicking on the top execution set folder.
Execution sets and script assignments that have not yet been downloaded (or have been changed since you last downloaded) to your device will display the download icon:
Once you have downloaded the execution set or the script assignment, the download icon will disappear.
You'll also notice that once a script assignment has been downloaded from the server to the client device, the script assignment icon will change from:
- White left corner with a green dot - this icon denotes that the script assignment is on the server and has not been downloaded.
to:
- solid green square - this icon denotes that the script assignment has been downloaded, and has not yet been altered on the client device.
You can view a list of all icons on the Entity Icon section of the Getting Started article.
Viewing and Running Tests
Once you have downloaded your script assignments, depending on the machine or device you are using, you can click or tap on the script assignment in the tree view to view or run your script.
The Script Description, Script Objective, Script Pre-Conditions, Script Post Conditions, Script Notes, all completed script custom fields and the run history will display on screen.
You can click or tap to view any of the previous run on the run history grid. The run history grid will provide you with some basic details including the Run Number, the Run By details, the status of each run and the Sync Status. The sync status will tell you whether the run has been recorded on the server or whether it only resides locally.
Starting a New Run
You can start a new run by clicking or tapping on the Create New Run button located above the run history grid. This will load the run screen which will provide you with all the custom fields scoped for script assignments and you'll also see your steps in a list view. You'll also see:
- The run number
- Step status icon (on each step)
- Step status bar (to the right of the scrollbar)
- The active step is highlighted with a blue border
- Step naviation and Result menu at the bottom of the screen
Similarly to executing a test run in ET, there is a text field for entering actual results. While a step is active you can click or tap on the step result at the bottom of the screen to set that step's status. If you pass a step, the next step will automatically be selected, otherwise the actual result field will be focused so that you can start typing. There are keyboard shortcuts for this screen:
- Ctrl+Up selects the previous step
- Ctrl+Down selects the next step
- Ctrl+P passes the current step
- Ctrl+F fails the current step
- Ctrl+B blocks the current step
- Ctrl+U marks the current step as undetermined
If you wish to quickly pass all steps, you can click or tap on the "hamburger" icon (≡) and select "Pass All".
Depending on the status for the step you'll notice that a status icon will be added to the step and the step background will be shaded. You'll also notice that the bottom status menu highlights the status of the current step. In the image below, Step 2 is highlighted and the status is failed. You'll also notice that the status bar is color coded according to the status of each step. This makes it easy to see the status of each step at a glance.
Passed
Failed
Blocked
Undetermined
Failing a Step and logging an Incident
To log an incident on a failed step, click or tap on the Incidents button under the Actual Results field on the step to open the incidents screen.
The incidents screen will display:
- Any incidents that are already linked to the step
- An area for creating a new incident, or linking to an existing incident that was either downloaded from the ET server or was previously created
Type in a name and click on the Create Incident button to open the incident create screen. Complete the fields and click on save to create a new incident and link it to the step.
As you type a name, you'll also see the list of existing incidents narrow down. Click "Link" on one of these if you'd prefer to link to an existing incident instead of creating a new one. For more information on linking incidents, see Incidents.
Close the window to return to your run. Once you have completed the run, the icon in the tree for the script assignment should now show 
which indicates that the script assignment has local changes which have not yet been uploaded to the server. See Synchronization to find out how to upload these changes back to the server.
Limitations
Rover does not currently support the following ET features:
- agile runs
- run timer