mobile testing Archives • Catch Software

Rover

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.

Rover

Incidents – Rover Plugin

Creating incidents during offline testing with Rover provides you with the ability to run tests from Enterprise Tester (ET) Platform Edition 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 ET. This article covers selecting incidents to synchronize and creating incidents during offline testing.

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.

Creating Incidents During Offline Testing Copying Incidents from ET to Rover

An internet connection is required for this task.

After logging into Rover, the navigator will display the execution set folders in the first project listed in the Enterprise Tester navigator.

In Enterprise Tester:

In Rover, the execution set icon is highlighted in green and 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 can only see projects defined in user permissions on the ET server.

Once the project is selected, review and select the execution sets and the incidents to download from the ET server.

On the left select the tab with the bug icon to view all incidents in a project:

Incidents that have not yet been downloaded (or have been changed since you last downloaded) to your device will display the download icon:

You can also select all by clicking or tapping on the Incidents folder at the top of the list:

Once an incident has been downloaded from the server to the client machine/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 serve and has not been downloaded,

To;

– Solid orange square – this icon denotes that the script assignment has been downloaded, and has not yet altered on the client machine/device.

You can view a list of all icons on the Entity Icon section of the Getting Started article.

The Incident can be viewed and updated by clicking on the incident in the list.

Managing Incidents

When running a test you can log an incident straight from the failed step ( see the Execution Sets article for more information of running test) by clicking on the Incidents button.

The incidents screen displays any incidents that are already linked to the script assignment on the same step, as well as an area for creating new incidents or linking to an existing incident that has been created or downloaded from the ET server. You can also create a new incident that will automatically be linked to the step.

Linking Incidents to the Script Step

From the Step Incident screen, you can view all linked incidents, link additional incidents or create a new incident.

Linked an incident to a step by clicking or tapping the ‘Link’ button associated with an existing incident. The ‘Linked Incidents’ section lists all incidents associated with the test step. Disassociate incidents from the step by clicking or tapping the ‘Unlink’ button.

You can filter the existing incidents by starting to type in the Summary field. This will automatically filter all incidents that match the text you have entered

Creating an Incident

Create an Incidents by adding a summary in the text field under ‘Create Link’ and then clicking or tapping on ‘Create Incident’.

The Incident Create screen will appear where you can all of your details including all the fields that have been configured in ET, attachments and comments. You can also select the External System Link ( Defect Tracker Project Link e.g. JIRA or TFS projects) that have been pre-configured in ET for your project. Selecting an external link synchronizes the incident with the external system ( JIRA or TFS) when uploaded to the ET Server.

When you have finished entering your details, click or tap on Save. You will return to the ‘Step Incident’ screen and the newly created incident will appear in the ‘Linked Incidents’ section.

You can now either close the screen to return to your run or log another incident.

Once you have completed your testing, you can synchronize your runs and incident back to the ET Server. The Synchroni z ation article provides details on how to complete this task.

Rover

Executing Tests Offline – Rover Plugin

Executing tests offline with Rover provides you with the ability to run tests from Enterprise Tester (ET) Platform Edition 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 ET. This article covers synchronizing and running script assignments.

Although internet access is not required to run tests in Rover, internet access is required for the following:

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 that familiarizes users with Rover.

Executing Tests Offline: 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 ET navigator.

In ET:

In Rover the execution icon is highlighted in green and the contents of the default project are displayed:

You can change the project by selecting from the drop down list. Like in ET, projects are organised into categories. Users can only see projects defined in the user permissions on the ET server.

Select the project then review and select execution sets 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.

The download icon displays on execution sets and script assignments that haven’t been downloaded (or have been changed since the last download):

Once you have downloaded the execution set or the script assignment, the download icon will disappear.

When a script assignment downloads from the server to a client device the ‘script assignment’ icon changes 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.

A list of all icons is in the ‘Entity Icon’ section of the Getting Started article.

Executing Tests Offline: 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 indicates location of the recorded run – on the server or only residing 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

There is a text field for entering actual results Similar to executing a test run in ET. 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. When a step is passed, the next step is automatically selected, otherwise information or notes are entered into the ‘Actual Result’ field. 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”.

A status icon will appear on the step with the background shaded depending on the status of the step. You’ll also notice that the bottom status menu highlights the status of the current step. The color-coded status bar indicates the status of each step. This makes it easy to see the status of each step at a glance. The image below shows ‘Step 2’ highlighted and the status as failed.

Passed

Failed

Blocked

Undetermined

Executing Tests Offline: 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:

All incidents already linked to the step
The screen to create a new incident or link an existing incident either downloaded from the ET server or 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

Rover

Getting Started With Offline Testing – Rover Plugin

Getting started with offline testing is easy with Enterprise Tester (ET) Platform Edition’s Rover Plugin – a mobile client for ET. Rover provides the flexibility to run tests and log incidents offline when internet access is limited or unavailable.

With Rover, you can:

Select the execution sets or individual script assignments to download to your Windows machine or device (internet access required)
Select the incidents to download to your windows machine or device (internet access required)
Run the required test (internet access not required)
Create or comment on incidents (internet access not required)
Link failing test steps to incidents (internet access not required)
Upload your data back to the ET server (when connected to the internet)

Getting Started With Offline Testing: Installing Rover Plugin

Rover is supported on Windows Operating Systems. For more information, please see System Requirements.

To install Rover download the application zip file from the Catch website. Unzip the files and run the ET Rover file (type is “application”, you will recognize it by its green icon). This will automatically launch Rover on your Windows machine or device.

The login screen will launch. You can pin the application to your start menu or your task bar to make it easier to launch the application.

Advice for Multi User Devices

If your machine or device is used by multiple people (e.g. pool resource), then we recommend that you install Rover into a directory that is associated with your personal profile rather than a shared directory.

The first time you log into the client, you will need to be able to connect to your ET server. This may mean that you need to be connected to the internet or be able to access your corporate or office network.

From the login screen, enter in your Server URL and your username and password.

If you do not have a ET mobile license applied to your installation of ET on the server, a message will appear alerting you that the license is missing or expired. If you see this message please contact your ET system administration to check your ET Rover license.

Getting Started With Offline Testing: Viewing your Projects

Once you have successfully logged into Rover, the default view shows the Execution Set of the first project in your project list, as shown:

You can change the project in view by selecting the project drop down. The project listed will depend on the projects your user account has access to on the ET server and will be listed in the same order as listed in the explorer navigator:

In ET, the navigator will show the execution sets as follows:

The project category structure and the order of projects is retained.

Getting Started With Offline Testing: Navigating Rover

The Navigator on the left side provides 4 view options:

Above the tabs you’ll notice a status icon. This will tell you if you are connected to the server or not.

With the icon shown as per the below image where the connections between the circles are not shown indicates there is no connection to the server.

The next image shows that you are connected to the server.

Getting Started With Offline Testing: Entity Icons

Rover has a number of entity icons that denote the state of the entity (script assignment or incident). The tables below show each icon and the state of the entity.

Script Assignments

Icon	State Description
	Synced (copied locally)
	Not Downloaded (only resides on ET server)
	Changed on Server (downloaded, but the entity has been updated on the server since the download)
	Local Version Changed (server has a copy but local version is newer)
	Both Server and Local Version Changed (each have a copy with changes that need merging)
	Deleted On Server (downloaded, but has since been deleted from the server)

Incidents

Icon	State Description
	Synced (copied locally)
	Not Downloaded (resides on ET server)
	Changed on the server (where an incident is downloaded but the entity has been updated on the server since the download).
	Not Uploaded (created locally, server doesn’t have a copy yet)
	The Incident is Changed Locally (server has a copy but local version is newer)
	Changed Incident on Both (each have a copy with changes that need merging)
	Deleted On Server (downloaded, but has since been deleted from the server)

Rover

Offline Testing System Requirements – Rover Plugin

The Rover plugin for Enterprise Tester (ET) Platform Edition allows users to work with ET data offline for testing. Getting started is easy and there are only a few simple system requirements for Rover – Offline Testing:

A working instance of Enterprise Tester Platform accessible over the internet or through a network (for uploading and downloading data).
Rover – Offline Testing license applied to Enterprise Tester Core Edition
A Windows device with the .NET Framework 4.5 installed

Enterprise Tester Platform Edition Offline Testing System Requirements

Rover is compatible with Enterprise Tester Core 4.10 and above. Enterprise Tester Platform must be installed on a server that is accessible either through the internet or through your office network. Access to Enterprise Tester Platform is required for downloading Execution Sets, individual Script Assignments and Incidents before going offline, and to upload results and updated or new incidents after testing.

Applying your Rover – Offline Testing License

To apply your Rover License, you will need to have Administrator rights to Enterprise Tester.

Navigate to the Admin tab, expand the Extensions folder and double click on Rover.

Add the license text ( if you do not have a license text, please contact Catch Sales) to the License Text field:

Operating System Requirements for Rover – Offline Testing (Client)

The client application supports the following Operating Systems:

Windows 10
Windows 8.1
Windows 8
Windows 7 SP1 (x86 and x64)
Windows Vista SP2 (x86 and x64)
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2 SP1 (x64)
Windows Server 2008 SP2 (x86 and x64)

Mobile Phones not supported

Windows Phone and Windows Mobile do not support .NET 4.5

.NET Framework

Rover requires .NET 4.5 to be installed.

When installing the .Net Framework 4.5 you have two options – either installing from a “web download” (a small download, which will then install only the components you require) or download a “redistributable”, which is a large file containing all the files necessary for the .Net Framework 4.5 to be installed on any machine.

If you plan on installing the Framework on more than one machine within your organization it is suggested that you use the redistributable, to avoid multiple downloads.

The web downloader can be downloaded from:

http://www.microsoft.com/en-us/download/details.aspx?id=30653

It is approximately 1mb in size.

The redistributable can be downloaded from:

http://download.microsoft.com/download/2/7/3/273CB528-CAB3-4E8D-88D2-4477F0A1DAE4/enu_vs_common/netfx_ult/dotnetfx45_full_x86_x64.exe

It is approximately 50mb in size.