Test Case Run Status

The Test Case Run status page displays Test Case Runs across all URLs and Projects in the Organization.

The list can be searched by Test Case name and can be filtered by:

  • Running: Test Case Runs which are currently running, or pending

  • Last hour: Test Case Runs which have completed within the last hour

  • Last day: Test Case Runs which have completed within the last 24 hours

  • Last 7 days: Test Case Runs which have completed within the last 7 days

  • Last 30 days: Test Case Runs which have completed within the last 30 days

When viewing "Running" Test Case Runs, the list will refresh automatically every 30 seconds. The list will not refresh automatically for other filter options.

The list displays:

  • Test Case name and number of scenarios. You can click this link to view or edit the Test Case (if you have permission to do so)

  • The names of the Medidata Rave URL and Project against which the Test Case is being run

  • The TrialGrid user who created the Test Set Run

  • The TrialGrid Queue for the Test Case Run, and the time the Test Case run was in the queue before being run (if it has started or completed), or the time it has been waiting (if it has not yet started), in minutes

  • The time the Test Case Run started (if it has started)

  • For running or pending Test Case Runs, the estimated run time of the Test Case Run. This is calculated by multipying the number of Test steps (or scenarios if the number of steps is not available) by the average time taken to execute a Test step (or scenario) by TrialGrid

  • For completed Test Case Runs, the time it finished and the elapsed time taken to run, in minutes

  • The status (Pending/Running/Cancelled/Failed/Passed) of the Test Case Run. You can click this button to view the Test Case Run (if you have permission to do so)

Warnings

Test Case Runs will be highlighted, and a warning symbol displayed next to the Test Case name if:

  • the number of scenarios in the Test Case is large. Test Cases with many scenarios will take a long time to execute, and might block other Test Cases from running. If possible the Test Case should be reduced in size.

  • the estimated run time is long, because there are many scenarios or steps. Test Cases which take a long time to execute might block other Test Cases from running. If possible the Test Case should be reduced in size.

  • the Test Case is running, or pending, more than once. If a Test Case is already being run, please consider cancelling earlier runs, to avoid blocking the queue for other users.

  • the Queue is full and is already running as many Test Cases as it can. Pending Test Case runs will wait until a slot in the Queue becomes availalble.

Queues

TrialGrid uses Queues to control how many Test Cases can be run at once. The queues are:

  • Single: this queue only runs one Test Case at a time, and will be used when more than one Test Cases have been selected to run with the 'Run concurrently' option turned off. This queue is not specific to a Project or URL; Test Cases must wait in line until other Test Cases earlier in the queue have been completed. This might include Test Cases being run by other Organizations, which you will not see in the list.

  • Shared: the shared queue will run multiple Test Cases at once. The maximum number of simultaneously running Test Cases for this queue is controlled by TrialGrid Ltd. This queue will be used if there is no dedicated queue specified.

  • Dedicated: identified by a number ('0001', '0002', etc), dedicated queues are allocated by TrialGrid Ltd to a Medidata Rave URL and/or to a TrialGrid Organization. These queues can be used to limit the number of simultaneous Test Case runs against a Medidata Rave URL, to avoid performance impacts on the Medidata Rave URL.