Summary

This article covers the Test node in Trial Manager. 


Table of Contents

Once the Trial Designer has completed and compiled the initial version of the trial within the Design node, the trial can move on to testing. The Test node in Trial Manager contains basic tools for flagging and loading versions of the DA as well as the Testing Manager.

DCT Connection

Refer to the DCT Connection instructions for more information on this form.

Flag Version

The Flag Version form can be used to flag versions for testing and unflag them if a version is flagged in error.

  1. On the Flag Version form, click the radio button beside the version that should be flagged for testing.
Note: Only those versions already committed to the repository will be included in the list.
  1. Choose ‘Flag Version’ or ‘Unflag Version’ from the actions dropdown list.
  2. Enter a comment to associate with the flagging action.
  3. Click the ‘Go’ button.

Load Version

After a version has been flagged for testing, it can be loaded to the Test server. The Test server is only accessible to certain users to provide a controlled environment for testing.

  1. On the Load Version form, click the radio button beside the version that should be loaded to the Test server.
  2. Click the ‘Load onto Test’ button.


Testing Manager

The Testing Manager is a centralized resource to monitor and control the flow of testing activities. The manager generates a table of a study’s testable components that describes their current stage of review in the testing environment. Provided with this table is a set of actions that can be applied to tested elements to advance, halt or regress their stage of testing.

Viewing Testing Results

This page provides an array of filters and utilities to manage these testing reports. The directions below outline how to configure them to your needs.

  1. Navigate to the ‘Testing Manager’ form under the Test node in the Form Navigation.
  2. Show Status: Select the testing status you wish to search for, otherwise leave the field set to ‘All’.
  3. By Tester: Select a name to filter by a specific tester, otherwise leave the field set to ‘All’.
  4. Compare Version: Choosing a version for this field will cause the results table to only include those items which have changed from the ‘Compare Version’ to the ‘New Version’.
Note: This function is similar to that of the 'View Changes' form in the Design node.

  1. Object ID: Enter an Id to filter for a specific object, otherwise leave blank.
  2. Change Type: Select the type of change you wish to search for, otherwise set to ‘All’.
  3. Test Phase: Select the testing phase that you wish to examine.
  4. New Version: Choose the commit version that is being tested.
  5. Object Type: Enter an object type to filter by, otherwise leave blank.
  6. Once these fields have been addressed, click the ‘Go’ button.


Filtering and Navigating Your Results

Once you have generated a table of testing results, there are several utilities that allow you to navigate your data and change how it is displayed. In the box labeled ‘Hide’, are several checkboxes that allow you to remove columns from the table. These are:

  • Version
  • Change
  • Old Value
  • New Value
  • Status

To hide these, click their corresponding checkbox, and then click the ‘Hide’ button. To undo any of these changes, click the ‘Clear’ button.


Also, on the ribbon at the top of your table are a few tools to assist in navigating this data. From here you may visit specific pages, as well as control how many results are displayed per page.

Carry Out Testing Procedures

The Testing Manager also allows the you to modify the testing status of components that are being tested. Using the dropdown list of actions above the table a user may mark an element as Passed, Failed, or they may Undo Previous Change.

To execute these actions:

  1. Click the checkboxes beside the elements you wish to modify.
  2. From the ‘Choose an Action — Press Go’ dropdown menu select the action you wish to apply.
  3. In the field labeled ‘Type Comment Here’ enter a short descriptive message justifying the action.
  4. Click the ‘Go’ button.


Exporting Your Results

The Testing Manager supports exports in both Excel and CSV formats. The buttons which trigger these actions appear only once you have generated a table of results. Clicking one of these buttons will open a prompt to download a compressed file containing your results in the chosen format.


Test Phases

This node allows the user to create and configure test phases. A test phase determines the testing schedule for elements in a version. This is done by adding testing elements to a phase. By default test phases include a single check of all testing elements in a version. Assigning testing elements allows you to change this to either 0, meaning that component is not tested, or some value greater than 1, requiring an element to be tested multiple times. The directions below describe this process.

Creating a Test Phase

  1. Navigate to the Test Phases form under the ‘Test’ node.
  2. Click the ‘Add Test Phase…’ link in the form-level action bar.
  3. Enter a name for the phase.
  4. Click ‘Check Data’ and/or ‘Save Form’.

Adding Testing Elements

  1. Navigate to the test phase you wish to modify in the Form Navigation.
  2. Click the ‘Add Testing Element…’ link on the form-level actions bar.
  3. Object Type Name: Enter the object type name that you wish to configure.
Note: These values must be identical to the object type names found in your dA.
  1. Times to Test: Enter an integer here for the number of times this particular object type should be tested. (’0′ to remove an object type from testing)
  2. Match Children: Check this box to apply the testing conditions to all object types that are a derivative of the object type entered in step 3.
Note: If the value entered for step 3 is 'export', checking this box would extend the requirement to 'export writer' as well.

Export Test Phases

Test phases may be exported at any time by navigating to the Test > Test Phases form and clicking the ‘Export’ button beside the label “Export Test Phases to File:”.

All Sites – Test

The site network is managed independently on each server. The All Sites link is initially created when the trial is setup – one tool on each cluster. This initial tool is meant as a starting point for building the appropriate site network for Design, Test, Approve and Production use. Trial Manager provides the ability to build a comprehensive site network as well as multiple independent tools. See All Sites – Design in the Design article for instructions on managing the site network.

Need more help?

Please visit the Fountayn Contact Information page.