RQM - Tiny
IBM.com Jazz.net Documentation


RQM-Tiny is a exercise to define a very minimal test management based on RQM.

Why? RQM is a powerful tool. The GUI as provided out-of-the-box reveal a lot of the functionality. For a just starting company this might be a bit overwhelming. It's certainly not a good start and fit for just starting. It confuses the customer. Suppose his organisation is at the level "I've got some test to run". He does not need an elaborated Test Plan, care for re-use, timelines or environments. This RQM-Tiny will give him a starting point. When the customer matures in the test process he can than turn on features and functions without any re-install or migration.

Test Flow

This chapter shows a basic flow for testing.

  1. Create a Test Plan - Plans are a collection of tests (Test Cases).
  2. Add Tests - to the Test Plan
  3. Add Test Scripts (test steps) to the Test Cases - (a 1:1 relation)
  4. (Re-)Run Test Cases - from the Test Plan. Use defaults in the Run Test Case

    Figure: Use run defaults.

  5. Report using
    1. Check Test Results section
    2. Reports - Shared Reports - Execution - "Execution Status using TCER Count", select only the relative Test Plan.

      Figure: A graphical report, select status of interest.

We are ignoring advanced topics like timelines, environments and re-use. Still when the occasion is there you can 'scale' this solution to a more comprehensive solution.


In this RQM-Tiny a lot of information and fields are hidden. Still the process remains the same. Basically:

Test Plan

Use Manage Sections to remove all sections with the exception of:

  1. Summary (can't hide)
  2. Test Cases (can't hide)
  3. Test Case Results

Figure: Tiny Test Plan template

In the Test Case section select the Change Column Display settings.

Figure: The Change Column Display settings

Remove all but (name is followed by percentage of width)

  1. ID - 10
  2. Name - 90

Figure: Select only the ID, Name

Similar for the Test Case Results, hide everything except:

  1. ID - 10
  2. Name - 50
  3. Last Result - 40

Select only the ID, Name and Last Result.

When you have the permission to edit you can simplify the GUI by renaming the TCER section

Figure: Renaming the Test Case Execution Records

Test Case

Similar for the Test Case Results, hide everything except the following sections:

  1. Summary
  2. Test Scripts

Test Script

You can't hide/simplified anything.


You could define and import templates for various artifacts.

Manage Project Properties

Execution States

Enable Passed, Failed
Disable all other.

Manage Application

Menu Organization

For the RQM-Tiny setup many options can be hidden in the menu.

Figure: RQM Simplified menu


  1. Requirements
  2. Planning
    1. Import
  3. Construction
    1. Browse
      1. Test Suites
      2. Test Data
      3. Keywords
    2. Create
      1. Test Suites
      2. Keywords
      3. Test Case Execution Record
      4. Test Suite Execution Record
      5. Test Data
    3. Import
      1. Test Cases
      2. Test Scripts
  4. Lab Management
  5. Builds
  6. Execution
    1. Browse
      1. Test Case Execution Record
      2. Test Suites
      3. Test Case Results
      4. Test Suite Results
      5. Test Cases
      6. Test Suites
      7. Execution Schedules
      8. Adapter Console
      9. Scheduled Jobs
    2. Create
      1. Create Execution Schedule
  7. Reports, not sure what to hide here..
  8. Change Requests