Test Execution

Anchor
Execution Tests Execution Tests

RoverX 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.

RoverX supports synchronizing both test runs and incidents with Enterprise Tester. This article covers synchronizing and running test runs.

Although internet access is not required to run tests in RoverX, internet access is required when performing the following;

• When downloading executions sets or individual test runs from Enterprise Tester server. Note: Any incidents that are associated to any of the test runs will be downloaded when the test run is downloaded.

• When uploading test run results and new incidents to Enterprise Tester server.

The Getting Started article provides an introduction to help users become familiarized with RoverX.

Downloading Execution Sets to RoverX

An internet connection is required for this task. Make sure you are in Online mode in RoverX.

1. Ensure Online Mode: Verify that you are connected to Enterprise Tester and in Online mode in RoverX.

2. Select a Project: Choose the desired project from the Project drop-down list.

3. View Execution Sets: The navigator will display the execution set folders and their test runs (excluding agile runs) in the selected project, as listed in the Enterprise Tester.

4. Download Execution Sets: Select the execution sets you want to download. The selected execution sets will be downloaded to RoverX for offline access.

This process allows you to work with Execution Sets offline after downloading them from Enterprise Tester.

Selecting a Project

• Open the Project Dropdown: Click on the Project dropdown list to view the available projects. Projects are organized into categories, similar to how they are structured in Enterprise Tester.

• View Accessible Projects: Users will only see projects that are defined in their user permissions on the Enterprise Tester server.

• Select a Project: Choose the desired project from the dropdown list. You can change the project at any time by selecting a different project from the dropdown.

• Review Execution Sets: Once you have selected a project, you can review and select the execution sets or individual test runs you wish to download from the Enterprise Tester server.

Image Added

Selecting execution sets 

• Expand Folders: By default, the folders are collapsed. The black button Image Added indicates that the folder can be expanded and contains sub-folders. Select this button to expand the folder.

  Image Added

• Folder Expansion Indicator: Once the folder can no longer be expanded, the button will change to the following icon Image Added.

• Expand All Packages: To expand all packages within a folder, right-click on the top execution set or any folder you wish to expand all sub-folders within.

Image Added

To view test runs in RoverX, follow these steps:

1. Expand the Folder:

   • Navigate to the folder where the test runs are located and expand it.

2. Select the Folder:

   • Click on the folder to display the Test Run table.

3. View Test Run Count:

   • The number of test runs in the folder is displayed in brackets next to the folder name.

Image Added

Execution sets and individual test runs that you have not yet downloaded to your device, or that have been changed since your last download, will display a download icon Image Added. This helps you identify which items need to be downloaded or updated.

Download execution sets

• Locate the Download Icon:

  • Find the download icon next to the folder or the individual script assignment you wish to download.

• Download Specific Items:

  • Click on the download icon for the specific folder or individual script assignment to initiate the download.

• Download All Items:

  • To download all execution sets and test runs, click on the download icon for the main Execution Sets folder.

While downloading, a progress bar will be displayed to show the download status.

Image Added

Once you have downloaded the execution set or the test runs the download icon will change to Image Added.
Image Added

To download one or more test runs, select the folder where the test runs are located.
Select the test runs you want to download.
Image Added
Select Download button. The selected test runs are downloaded.

Image Added

Test Run Details 

When viewing test run details in RoverX, they are displayed on the right-hand side of the screen. The following columns are included in the test run details:

Image Added

• Downloaded  -  Indicates whether the test run has been downloaded to your local machine or is still stored on the Enterprise Tester server.
• Assignment -   The name or identifier of the test run.
• Status Server - Displays the current status of the test run on the Enterprise Tester server.
• Status Local -Shows the current status of the test run on your local machine.
• Sync Status -  Tells you whether the test run has been recorded on the server or if it only exists locally. If the status is "local," the test run will be uploaded to Enterprise Tester
                          server during the next synchronisation.

Viewing and Running Tests

Once you have downloaded your test runs, you can click or tap on the test run in the table, depending on the device you are using, to view or execute your script.

Displayed Fields

When you view a test run, the following fields will be displayed on the screen. Note that if any fields are blank in Enterprise Tester, they will not appear in RoverX.

• Script Description: A detailed description of the test script.
• Script Objective: The goal or purpose of the test script.
• Script Pre-Conditions: Any conditions that need to be met before executing the test script.
• Script Post Conditions: Conditions expected after the test script has been executed.
• Script Notes: Additional notes related to the test script.
• Run History: The last two test executions will be shown for reference.

Image AddedRun History

You can choose to view any of the previous runs on the run history grid. The run history grid provides some basic details, including:

• Run Number: The identifier for each test run.
• Run By: Details of who executed the run.
• Status: The status of each test run.
• Sync Status: Indicates whether the run has been recorded on the server or if it only resides locally.
• Incidents: Any incidents associated with the test run.

Starting a New Run or Completing an Existing Run

• Starting a New Run
  You can start a new test run if the latest test run has been completed on the server or locally. To do this, simply select the Create New Run button located to the left of the run history grid.

• Completing an Existing Run
  If the latest test run is incomplete (marked as "Not Run" or "In Progress"), you can continue with that test run and complete it instead of starting a new one.

Image Added

When you load the Test Execution screen, you will see the test steps displayed in a list view. This screen provides the following details:

• Run Number: The identifier for the current test run.
• Number of Steps: The total number of steps in the test run (displayed in brackets).
• Test Run Name: The name of the current test run.
• Test Run Status: The current status of the test run.
• Back Button: Allows you to navigate back to the previous screen.
• Step Result Menu: Located at the bottom of the screen, for selecting the results of each test step.
• Custom Field Icon: Appears if there are any custom fields associated with the test run.

Image Added
Viewing and updating Custom fields

If your test run includes custom fields, you will see this button Image Added in the header. Clicking on this icon will close the Test Steps panel and display all the custom fields, allowing you to view and update them accordingly.

Image Added

You can then update any of the custom fields and select the Save button. A confirmation message will be displayed to confirm that the data has been saved successfully.
Select OK button.
Image Added

To close the Custom Fields panel and return to the Test Steps, select the Image Added button.

Just like in Enterprise Tester, the Test Execution screen includes a text field for entering Actual Results for each test step.

While a step is active, you can select the Step Result option at the bottom of the screen to set the status for that specific step. Once you select a status for a test step, the screen will automatically move to the next step in the list.

Hyperlinks and local paths can be added in the Actual Result field.

Keyboard Shortcuts for Test Execution

To enhance efficiency while working with test steps, you can use the following keyboard shortcuts:

• Ctrl+P: Mark the current step as Passed.
• Ctrl+F: Mark the current step as Failed.
• Ctrl+B: Mark the current step as Blocked.
• Ctrl+U: Mark the current step as Undetermined.

These shortcuts allow you to quickly update the status of the current test step.

Using Shortcut Keys to Set Step Status

You can streamline your testing process by using shortcut keys to set statuses for multiple steps at once.

For example, if you want to mark all steps in the test run as Passed:

1. Press <CTRL+A> to select all steps.
2. Then press <CTRL+P> to mark all selected test steps as Passed.

This functionality allows you to quickly update the status of multiple steps without having to select each one individually.

Copying and Pasting Text

RoverX allows you to copy and paste text from external sources, such as Excel, directly into the Actual Result field. To do this:

1. Copy the desired text from your source (e.g., Excel) using Ctrl+C.
2. Navigate to the Expected Result field in Rover.
3. Paste the copied text into the field by using Ctrl+V.

This feature helps streamline the process of entering expected results by enabling quick transfers of text data.

You can also copy the Expected Result to the Actual Result field. 

Image Added  

To do this open the Actual Result field and then select CTRL+V and it will paste it.
Image Added
   

Then click on the X button to close the Actual Result pop up  window. Note: Clicking the X button saves the changes to Actual Result field.

Image Added

Test Step and Test Run Statuses

In RoverX, test step and test run statuses are consistent with those in Enterprise Tester.

Status Representation

• Icons and Color Coding: Statuses are represented by icons and the color of the test step row. Hover over an icon to view the detailed status.
• Test Run Statuses: In addition to the statuses used for individual test steps, test runs have an additional status: In Progress.

Overall Test Run Status

The overall status of a test run is automatically determined based on the statuses of its individual test steps.

Image Added Passed

Image Added Failed

Image Added Blocked

Image Added Undetermined

Image AddedIn Progress

Image Added

Adding Attachments to Test Steps

You can attach one or more files to a test step by following these steps:

1. Select the Attachment Button Image Added: Click the button located in the Attachment column of the test step.
2. Manage Attachments Popup: This action will open the Manage Attachments popup, where you can upload and manage your attachments.
3. Select Files: Click the Image Addedbutton within the popup to find and select your files. You can select multiple files at once.
4. Upload and Display: The selected files will be uploaded, and their paths will be displayed in the popup.

This feature allows you to include relevant files and documents with each test step for better documentation and reference.

Image Added

Managing Attachments

If you scroll to the right within the Manage Attachments popup, you have the following options for each attachment:

• View: Click to open and view the attached file.
• Delete: Click to remove the attachment from the test step.

These options allow you to easily manage the files associated with your test steps.

Image Added
Select the X button to return to the Test Run.
Once you return to the Test Run screen, an icon will appear to indicate that there are attachments for the test step.
Hover over the Image Addedicon to see the number of attachments associated with the test step.

Image Added

Clicking on the Image Added will open the Manage Attachments popup where you can view or delete existing attachments.

Incidents

Anchor
Incidents Incidents

RoverX is a tool that enhances the testing capabilities of Enterprise Tester, particularly useful for remote or offline environments. Here’s a summary of its key features and requirements:

Key Features:

• Offline Testing: Allows running tests without the need for internet connectivity, ideal for remote locations.
• Synchronization: Supports synchronizing both script assignments and incidents with Enterprise Tester.
• Creating Incidents: Incidents can be created during the testing process.

Internet Connectivity Requirements:

• Downloading Data: Internet access is required for downloading test executions, test runs, and associated incidents from the Enterprise Tester server.
• Uploading Data: Internet access is also necessary for uploading test run results and new incidents to the Enterprise Tester server.

Limitations:

RoverX does not currently support the following Enterprise Tester features:

• Agile Runs: RoverX does not support agile runs, which are specific to agile methodologies and workflows.

• Run Timer: The run timer feature, used to track the duration of test runs, is not available in RoverX.

These limitations mean that certain features available in Enterprise Tester will not be accessible while using RoverX.

The Getting Started article provides an introduction to help users become familiarized with RoverX.

Managing Incidents

In RoverX, you have the option to manage incidents by either creating new ones or linking them to existing downloaded incidents.

1. Create New Incidents: You can create new incidents directly within RoverX if needed. This allows you to document and manage issues encountered during test runs.

2. Link to Existing Incidents: Alternatively, you can link to an existing downloaded incident. This is useful for maintaining continuity and associating new issues with previously documented incidents.

Create Incident

To log an incident on a failed test step, follow these steps:

1. Select the Incident Button: Click the Image Addedbutton in the Incident column for the test step that has failed.

2. Access the Create Incident Screen: The Create Incident screen will be displayed.

3. Default Summary: By default, the Test Script Name will automatically be populated in the Summary field. You can choose to keep this default summary or edit it as needed.

4. Fill Out Required Fields: All fields that are present in Enterprise Tester will be visible on the Create Incident screen. If a field is mandatory in Enterprise Tester, it will also be required in RoverX.Image Added

5. Save the Incident: Once you have completed entering the details, click the Save button. The Create Incident screen will close, and you will be returned to your test run.

6. Incident Icon: A bug icon will now be added to the test step, indicating that an incident has been created for this step.Image Added

External Jira Links

When creating an incident, you have the option to link it to an external Jira system, provided that integration has been configured in Enterprise Tester for your project.

1. Select External Jira System Link: If your project has been configured with external Jira system links in Enterprise Tester, you can select the appropriate link from the Synchronize To: dropdown list.

2. Automatic Selection: By default, the first external Jira system link configured in Enterprise Tester will be selected. If there are multiple Jira system links, choose the one that is appropriate for your needs.

3. Sync with Jira: Once selected, the incident will be synchronized with your external Jira system when the incident is uploaded to Enterprise Tester.

4. No Jira Integration: If Jira integration is not set up with Enterprise Tester, there will be no options available for the Synchronize To: field.

This allows you to ensure that incidents are properly linked and synchronized with your external Jira system if configured.

Image Added

The following are drop down lists and can be changed. The values in the fields are from the Project in Enterprise Tester.

Priority:

Image Added

Status:

Image Added

Type:

Image Added

Resolution:
By default the Resolution field is blank. But you may if change this if you need to.

Image Added

Assigned To: 
Only Active users in Enterprise Tester are displayed. If the Assigned To field is mandatory it will default to the user that is logged in.

Image Added

Note: If there is nothing in the Assign To: field , this usually means you have not synced the users from Enterprise Tester to Rover.
To do this, make sure you are connected to the Internet, select Online mode and click on the Login button. This will download all active users from Enterprise Tester.

Description field
The Description field will  be populated with the same data that is created in Enterprise Tester when you create an incident from a test step.

In Enterprise Tester:

Image Added

In Rover:

Image Added

Editing an Incident:

You can edit an incident while it is still local (i.e., has not been synchronized to Enterprise Tester).

1. Open the Incidents Pop-up: Click the Image Addedbutton to display the Incidents pop-up. This pop-up shows all incidents linked to the selected test step.

2. View Incidents: The Incidents pop-up will display all incidents associated with the selected test step.Image Added

3. Edit an Existing Incident: To modify an existing incident, select the incident from the list and make the necessary changes.

4. Create a New Incident: If needed, you can also create a new incident from the Incidents pop-up.

5. Save Changes: After editing or creating incidents, ensure to save your changes to update the local data.

Linking Incidents to a Test Step

You can view all linked incidents, link additional incidents, or create a new incident. Here’s how to manage incident links:

1. Select the Incident Button: Click the Image Addedbutton in the Incident column for the test step that has failed.

2. Access the Create Incident Screen: The Create Incident screen will be displayed.

3. Open Link/Unlink Incidents Screen: Click on the Link/Unlink Incidents link at the top left of the Create Incident screen.
   Image Added

4. View Link/Unlink Incidents Screen: The Link/Unlink Incidents screen will be displayed with the following elements:

   • Step Description: Shows details about the current test step.
   • Search Bar: Allows you to search for incidents.
   • Back Button: Navigate back to the previous screen.
   • Linked Incidents: Lists all incidents already associated with the test step.
   • All Incidents: Displays all local incidents that can be linked.
   • Link Button: Link incidents to the step by selecting this button.
   • Unlink Button: Remove incidents from the step by selecting this button.
     Image Added

5. Filter Incidents: To filter existing incidents, start typing in the Summary field. The list of incidents will automatically update to show only those that match the text you have entered.
   Image Added

6. Link Incidents: To add incidents to the test step, select the Link button next to the desired incident in the All Incidents section.

7. Unlink Incidents: To remove incidents from the test step, select the Unlink button next to the incident in the Linked Incidents section.

Returning to the Test Execution Screen

To return to the Test Execution screen after managing incidents:

1. Navigate Back: Click the Back button to return to the Create Incident screen.

2. Return to Test Execution: Click the Back button again to navigate back to the Test Execution screen.

This process ensures that you exit the incident management screens and return to your test run view.

Synchronizing Runs and Incidents

Once you have completed your testing, you can synchronize your runs and incidents back to Enterprise Tester. For detailed instructions on how to perform synchronization, please refer to the Synchronization article.

Synchronization

Anchor
Synchronisation Synchronisation

RoverX provides a convenient way to copy your Execution Sets and Incidents to your client machine or device, enabling offline testing. When you are reconnected, you can upload your test runs and incidents back to Enterprise Tester.

To synchronize your Execution Sets and Incidents:

1. Ensure Connectivity: You will need an internet connection or access to Enterprise Tester, which may require being connected to your office network. This connectivity is necessary for both the download and upload processes.

2. Download Execution Sets and Incidents: When connected, download the necessary Execution Sets and Incidents to your local machine for offline use.

3. Upload Changes: Once you have completed your testing, you can synchronize (upload) your Execution Sets and Incidents back to Enterprise Tester.
   
   

Uploading Entities to Enterprise Tester

Once you have completed your testing, you can upload your runs and incidents back to Enterprise Tester by navigating to the Sync Dashboard.

To Upload Your Runs and Incidents:

1. Access the Sync Dashboard:

   • Navigate to the Sync tab. Note that the Sync Dashboard can only be accessed when you are in Online mode and connected to the Enterprise Tester server.

2. Start Synchronization:

   • Clicking on the Sync Dashboard will automatically initiate the synchronization process, uploading your runs and incidents to Enterprise Tester.

Sync Dashboard at a Glance

The Sync Dashboard provides a comprehensive view of the synchronization status, allowing you to monitor upload progress and ensure successful data transfer.

Image Added

• Progress Bar: Displays the sync progress.
• Runs to be Synced: Number of test runs to be synced, grouped by status.
• Runs Synced: Number of successfully synced test runs (highlighted in green).
• Runs Failed to Sync: Number of test runs that failed to sync (highlighted in red).
• Incidents to be Synced: Number of incidents per test run status to be synced.
• Incidents Synced: Number of successfully synced incidents (highlighted in green).
• Incidents Failed to Sync: Number of incidents that failed to sync (highlighted in red).
• Attachments to be Synced: Number of attachments to be synced, grouped by test run status.
• Attachments Synced: Number of successfully synced attachments (highlighted in green).
• Attachments Failed to Sync: Number of attachments that failed to sync (highlighted in red).
• Incidents to be Linked: Number of incident links to be synced.
• Incidents Linked: Number of successfully synced incident links (highlighted in green).
• Incidents Failed to Link: Number of incident links that failed to sync (highlighted in red).

Synchronization Process for Completed Test Runs

Anchor
Synchronization Process for Completed Test Runs Synchronization Process for Completed Test Runs

To ensure smooth and accurate synchronization to Enterprise Tester,  the synchronization process is as follows:

1.Upload Completed Test Runs:

• Completed test runs are uploaded first.
• Test runs marked "In Progress" or "Not Run" will be uploaded later when selected by the user.
  
  

Image Added

2. Upload Incidents Associated with Test Runs:

• After test runs are uploaded, associated incidents are uploaded.
• The dashboard displays both incidents to be synced and incidents that have been synced.

Image Added

3. Upload Attachments:

• Attachments related to test steps and incidents are uploaded next.
  Image Added

4. Link Incidents to Test Runs:

• Finally, incidents are linked to their corresponding test runs to complete the synchronization process.

Process for Incomplete Runs

After all completed test runs, attachments, and incidents are uploaded:

1. Notification and Review:

   • A button will blink on the screen.
   • A table will display test runs that are "In Progress" or "Not Run."
     Image Added

2. Decision:

   • Review the incomplete test runs.
   • Decide whether to upload them or return to Test Execution Image Added to complete them.

3. Upload Incomplete Test Runs:

   • If you choose to upload, they will sync to Enterprise Tester with the same status.
   • To upload, simply select the Image Addedbutton. The sync process will follow the same order as the Synchronization Process for Completed Test Runs. Once the upload is completed, the table will disappear.
     
     Image Added