Enterprise Tester Rover is a plugin that gives users the flexibility to test anywhere. With Rover, users will now be able to access Enterprise Tester’s core features whether you’re working offsite or all the way in outer space!
Panel |
---|
Features
|
Panel | ||
---|---|---|
| ||
|
Panel | |||||
---|---|---|---|---|---|
System RequirementsRover is a plugin for Enterprise Tester that allows users to be able to work with Enterprise Tester data offline. Getting started is easy and there are only a few simple requirements:
Rover is compatible with Enterprise Tester 6.4 and above. Enterprise Tester must be installed on a server that is accessible either through the internet or through your office network. This is so that you can access Enterprise Tester to download the Execution Sets, individual Script Assignments, Incidents, and before going offline as well as being able to access Enterprise Tester again to upload your results and updated and new incidents. Applying your Rover LicenseTo 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 Systems (Client)The client application supports the following Operating Systems:
.NET FrameworkRover requires .NET 4.5 to be installed. When installing the .Net Framework 4.5 you have two options - either install from a "web download" (a small download, which will then install only the components you require) or you can 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 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 |
Panel | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Getting StartedEnterprise Tester Rover is an offline mobile client for Enterprise Tester. Rover gives you the flexibility to run your tests and log incidents offline when internet access maybe limited or unavailable. With Rover, you can:
Installing RoverRover 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 https://catchsoftware.com/enterprise-tester-platform-edition/rover/. 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.
The first time you log into the client, you will need to be able to connect to your Enterprise Tester 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 Enterprise Tester Server URL, username and password. If you do not have a Rover license applied to your installation of Enterprise Tester on the server, a message will appear alerting you that the license is missing or expired. If you see this message please contact your Enterprise Tester system administration to check your Rover license. Download Enterprise Tester Users to Rover
Once the User Sync has completed the following message will be displayed on the screen. Click on the OK button to continue. Viewing your ProjectsWhen you log in to Rover for the first time Project field will be blank. To access the projects from Enterprise Tester that you have permission to, click on the down arrow (above the search field). The Execution Set and Packages will be displayed and listed in the same order as the explorer navigator in Enterprise Tester. You can change the project in view by selecting the project drop down. The project The projects listed will depend on the projects your user account has access to on the ET server and will be in Enterprise Tester. In Enterprise Tester, the navigator shows Explorer Tree s hows the following: The project category structure and the order of projects is retained. The next time you log in to Rover the last project selected will be displayed by default. Navigating RoverThe Navigator on the left side provides 5 options: Above the tabs you'll notice a status icon. This will tell you if you are connected to the server or not. The following icon indicates that you are not connected to the server. The next image shows that you are connected to the server. Search Bar Enter search criteria in the Search field and press Enter on your keyboard or select the Search icon. Entity IconsRover has a number of entity icons that denote the state of the (script assignment or incident). The tables below show each icon and the state of the entity. Script Assignments
Incidents
|
Panel | ||||||
---|---|---|---|---|---|---|
Test Execution
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.
The Getting Started article provides an introduction to help users become familiarized with Rover. Copying Scripts and Execution Sets to RoverAn internet connection is required for this task. After logging into Rover, and selecting a project, the navigator will display the execution set folders and their script assignments (but not their agile runs) in the selected project listed in the Enterprise Tester navigator. In Enterprise Tester: In Rover, the execution icon is highlighted in green and the packages and any script assignments of the selected project are displayed: You can change the project by selecting from the drop down list. Projects are organised into categories, just like in Enterprise Tester. Users will only be able to see projects that are defined in their user permissions on the Enterprise Tester server. Once the project is selected, you can then review and select the execution sets you wish to download from Enterprise Tester server. By default the folders are collapsed. The white button shows that the folder can be expanded and has sub-folders. Click on this to expand the 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 . To download execution sets, click on the download icon for the folder or the individual script assignment you wish to download. You can also download all execution sets and script assignments by clicking on the download icon for the Execution Sets folder. 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 TestsOnce 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 following fields will be displayed on the screen. If any of the fields are blank in Enterprise Tester then the fields will not be displayed in Rover when viewing.
You can choose to view any of the previous runs 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, the Sync Status and any Incidents associated to the Test Run. The sync status will tell you whether the run has been recorded on the server or whether it only resides locally. Starting a New RunYou can start a new run by selecting 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:
Similarly to executing a test run in Enterprise Tester, there is a text field for entering Actual Results. While a step is active you can select 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.
Rover allows copying and pasting text from another source i.e. Excel and pasting it into the Expected Result field (by using CTRL+V). You can also copy all of the Test Step details and paste them into the Expected Results field. Hyperlinks and local paths can be added in the Actual Result field. 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 Undetermined Failing a Step and logging an IncidentTo 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 Create Link screen. The Create Link screen will display:
You can either edit the Summary field (Bug Name) or leave it as the default name. Once you have selected Save the window will close and you will be returned to your run. Limitations Rover does not currently support the following Enterprise Tester features:
|
Panel | ||||||
---|---|---|---|---|---|---|
Incidents
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 This article covers selecting incidents to synchronize and creating incidents during testing. Although internet access is not required to run tests in Rover, internet access is required when performing the following:
The Getting Started article provides an introduction to help users become familiarized with Rover. Copying Incidents from ET to RoverAn internet connection is required for this task. After logging into Rover, the navigator will display the execution set folders in of the first last project listed in the Enterprise Tester navigator. In Enterprise Tester: the logged-in user was working with. The Execution Set tab 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 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 To review and select the execution sets and the incidents you wish to download from the ET server.On the left select the tab with Enterprise Tester select the bug icon to view all incidents in a project:in the left hand menu. 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:
You'll also notice that once a 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 IncidentsWhen 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 will display any incidents that are already linked to the script assignment on the same step and an area from creating a new incident or linking to an incident that was downloaded from the ET server or was previously created. You can also create a new incident that will automatically be linked to the step. Linking Incidents to the Script StepFrom the Step Incident screen, you can view all linked incidents, link additional incidents or create a new incident. Incidents linked to the step can be added by clicking or tapping on the Link button associated with an existing incident. All incidents that are already associated with the step are listed in the Linked Incidents section. These can be disassociated from the step by clicking or tapping on 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 IncidentIncidents are easily created 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. If you select a external link, the incident will be synchronized with your external system ( JIRA or TFS) when the incident is uploaded to the ET Server. When you have finished entering your details, click or tap on Save. You will be returned to the Step Incident screen and your 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 Synchronization article provides details on how to complete this task. |
Panel | ||||||
---|---|---|---|---|---|---|
Synchronization
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 EntitiesDownloads 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 ServerOnce 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 SynchronizationSynchronization requires matching the Enterprise Tester ID for each entity to successfully synchronize between Rover and the Enterprise Tester server. Some changes made to the Enterprise Tester server between downloading to Rover and uploading results and updates from Rover may cause synchronization issues. Below are some causes of synchronization failure:
Troubleshooting SynchronizationIf you are having trouble diagnosing the cause of your synchronization failure, please send a copy of your Rover log file for the day the 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. |