RQM - Initialize Test Execution
IBM.com Jazz.net Documentation developerWorks CLM Artifacts

Contents

  1. GUI Execution
  2. Batch
  3. Other Resources

 

This page discuss the various options to start a test from RQM.

The beauty is that it does not matter how a test is initiated. From the RQM GUI, batch or triggered by a build completion. All results are gathered, and reporting can be done in the same way.

GUI Execution

There are many ways you can initiate a test execution. The most important one's are described here.

Test Case

Every test case has a run button, not the test script.

Warning! If the execution is not associated with the test plan, the results will NOT be included in any report.

On the fly a test case execution record will be created.

Figure: Run of a test case

Figure: Selection or Configuration of a TCER (the CMD1 agent is not yet started).

After selecting the OK the test execution can be monitored. This can also be viewed from the Execution Console.

Figure: The Execution Console.

Test Case Execution Record

The TCER has all the information contained, so no additional questions are asked.

Figure: The Test Case Execution Record can be executed. Here listed from within the Test Case itself.

Test Suite

A Test Suite is an ordered list of Test Cases.

Test Suite

Test Suite Execution Record

Similar to Test Case. When executed, any needed Test Case Execution Records are automatically generated.

Test Suite Execution Record.

Batch Execution

You can let the machines run. Execution is done based on various triggers set in the applications.
It's a component of DevOps.

Schedule based on Date/Time

The RQM Schedule is the 'build engine' for testers.

You can schedule a run triggered on:

  1. Time
  2. Build Completion

An execution schedule can be created from the Execution menu:

  1. Select Execution
  2. Select Create Execution Schedule

Figure: The Execution Schedule overview to set the 'trigger' for the schedule.

The Test Cell is explained in the RQM Lab management part.

After than you can add one or more of:

When triggered by time, the Execution Console is empty until a few seconds after the set timer.

Figure: The Execution Console when a Test Suite is initiated by time.

RTC Build Completion

With this option RQM "waits" until a build is completed.

Initiate execution as a result of a successful developer-build. The developers can define their own build-structures. Based on their success we can initiate tests.
Make note of the following:

  1. The build machine is free to run next builds
  2. That a personal build will not trigger a testing cycle!
  3. Developer builds can be setup in such a way that they are only triggered when code is checked in.

Figure: The Execution Schedule overview to set the 'trigger' by a succesful build.

RTC Build Completion & Urbancode

When one references from RQM directly the build, the build must be completed. But tests are executed against a deployed application. If the build is to be deployed, it will take time.

This option is the solution for that problem. In the last step of the RTC Build the Urbancode deployment process is started. Within the deployment process the RQM tests are initiated. Thus these are executed after deployement-completion.

Urbancode

Other Sources

Other sources on integrating builds:

ANT starts RQM Suite

Tip! If you don't use RTC for build management you can leverage the ANT-RQM integration.
See here.

It's possible to start a RQM test from ANT. More information can be found here.
Make note of the following:

  1. The build machine will wait for ending of RQM execution (to be checked).
  2. That a personal build will (normally) trigger a testing cycle!
  3. Developer builds can be setup in such a way that they are only triggered when code is checked in.

Other Resouces