RegisterLog In to Jazz.net dW
Download 4.0.6 Release
February 28, 2014
Try it in the Sandbox
Buy it | Questions?

Rational Quality Manager

Quality management Manual testing Continuous improvement

Rational Quality Manager 4.0 M7 Milestone

Early Access Milestone | January 30, 2012
This is not the recommended version. We recommend Rational Quality Manager 4.0. This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

The downloads for this milestone are no longer available.

Rational Quality Manager 4.0 M7 New And Noteworthy

Rational Quality Manager 4.0 M7 "New and Noteworthy"

Here are some of the most noteworthy items in Rational Quality Manager 4.0 M7. In addition, this milestone includes any new features that were added for Rational Quality Manager 3.0.1.2.

Rational Team Concert, Rational Quality Manager, and Rational Requirements Composer share a common set of server applications with each product offering role-based licenses that permit access to different capabilities provided by the applications. Therefore you should also read the New & Noteworthy page for Jazz Foundation 4.0 M7 and unless you elect to not install the Change & Configuration Management and the Requirements Management applications, you should also read the pages for Rational Team Concert 4.0 M7 and Rational Requirements Composer 4.0 M7.

Table of contents

Traceability and live views
Integrations and requirements
Planning
Reporting
Test execution
User assistance
M7 task guide

Also included are descriptions of the new features in the previous milestones. See New & Noteworthy in RQM 3.5 M5, New & Noteworthy in RQM 3.5 M3, and New & Noteworthy in RQM 3.5 M1.


Traceability and live views

  • Added a new Test Plans Execution Status dashboard viewlet (story 56425).
  • Aspect views are now available in secondary lists such as the Test Cases section in the test plan editor (work item 59557).
  • Provided remove link capability in traceability displays (work item 59533).
  • Provided configurable columns for save queries and column re-ordering capability and quick show/hide columns control (work item 60332).
  • Traceability and execution status columns are now available in all aspect views (work item 59532).

Integrations and requirements


Planning

Reporting

  • 8 new Birt reports are available for test suites:
    • TSER Listing
    • Test Case Results Details of Test Suite Results
    • TSER Status using Test Case Count
    • TSER Status using Weight
    • TSER Status by Owner using TSER Count
    • TSER Status by Owner using Weight
    • Execution Status by Test Suite using TSER Count
    • Execution Status by Test Suite using Weight

    These reports will not automatically appear after you migrate existing projects, only in new projects. To add them to existing projects, you must deploy them to the server as report templates and then create new reports based on these templates. See the online help for instructions on how to deploy and instantiate report templates.

    Each report uses live data, rather than data warehouse data. Several of the reports allow you to drill down into other reports to access more detailed information. For more information about each report, see the table, report descriptions, and report examples below.

    Name Type Dashboard version Drill-down Description
    TSER Listing Execution Yes Yes Lists the test suite execution records, based on selected parameters.
    Test Case Results Details of Test Suite Results Execution No Yes Lists the test case execution records of the given test suites, based on selected parameters. 
    TSER Status using Test Case Count Execution No Yes Displays the execution status of test suites, measured against test case count for each execution result status.
    TSER Status using Weight Execution No No Displays the execution status of test suites, shows test cases count by their status, based on selected parameters.
    TSER Status by Owner using TSER Count Execution No Yes Displays the execution status of test suite execution records by its owner, measured against TSER count.
    TSER Status by Owner using Weight Execution No Yes Displays the execution status of test suite execution records by its owner, measured against weight.
    Execution Status by Test Suite using TSER Count Execution No Yes Displays the execution status by test suites, measured against TSER count.
    Execution Status by Test Suite using Weight Execution No Yes Displays the execution status by test suites, measured against weight.

    TSER Listing

    This report lists the test suite execution records, based on selected parameters. Only the test suite execution records that are included in a test plan in the project area are listed in the report. In addition to the basic information about the test suite execution records, you can also see the total number of test cases and how many test cases are passed, failed, blocked, in progress, inconclusive and not started in the last execution result of the test suite execution record. You can also easily get the aggregate counts grouped by test plan and test suite in the test plan from the report. The last row of the report summarizes the test cases counts for all of the test suite execution records listed in the report.

    Test Case Results Details of Test Suite Results

    This report lists the execution status of test suites, and shows test cases count by their status, based on selected parameters. This report focuses on the test case execution results details of the selected test suite execution result. Only the last execution result of the selected test suites will be shown, and the test case execution results according to these test suite execution results will be listed. You can also see the total number of points of passed, failed, blocked, in progress, inconclusive, not started, perm failed and deferred in the last execution result of the test suite execution record.

    TSER Status using Test Case Count

    This report displays the execution status of test suites, measured against test case count for each execution result status. Only the test suite execution records that are included in a test plan in the project area are be displayed in this report. You can see the total number of test cases and how many test cases are passed, failed, blocked, in progress, inconclusive and not started in the last execution result of the test suite execution record. You can also easily get the aggregate counts grouped by test plan and test suite in the test plan from the report. The last row summarizes the test cases counts for all of the test suite execution records listed in the report.

    TSER Status using Weight

    This report displays the execution status by test suite execution records, measured against weight. This report focuses on the weight distribution of the last execution results of given test suite execution records, including the points not started. If the test suite execution record is never run, its weight number is counted into points not started.

    TSER Status by Owner using TSER Count

    This report displays the execution status of test suite execution records by its owner, measured against TSER count. The bar chart will show the TSER count for the chosen TSER owner. If the TSER has no owner assigned, this TSER result will be counted as "Unassigned". By clicking a bar in the report, you can drill down to the "TSER Status using Test Case Count" report to show the test case results' status.

    TSER Status by Owner using Weight

    This report displays the execution status of test suite execution records by its owner, measured against weight. By clicking a bar in the report, you can drill down to the "TSER Status using Weight" report to show the weight distribution of execution results of the owner's test suite execution records where the point matching to the point category of the bar is not 0. The bar chart will show the weight distribution of the last execution results of all test suite execution records of given owners, including the points not started. If one test suite execution record is never run, its weight number is counted into points not started.

    Execution Status by Test Suite using TSER Count

    This report displays the execution status by test suites, measured against TSER count. The bar chart will show the TSER count of the last execution results of all test suite execution records of given test suites, including the points not started. By clicking a bar in the report, you can drill down to the "TSER Status using Test Case Count" report to show the test case result details for execution results of the test suite's test suite execution records.

    Execution Status by Test Suite using Weight

    This report displays the execution status by test suites, measured against weight. The bar chart will show the weight distribution of the last execution results of all test suite execution records of given test suites, including the points not started. If one test suite execution record is never run, its weight number is counted into points not started. By clicking a bar in the report, you can drill down to the "TSER Status using Weight" report to show the weight distribution of execution results of the test suite's test suite execution records where the point matching to the point category of the bar is not 0.

  • Usability improvements have been made to Birt reports related to parameters, presentation of graph data in additional tables, and the About descriptions (text to be provided in M8 and RC1).
  • Data Collection tasks have been updated to support schema changes. Also, data collection now includes all custom attributes, all categories, and all quality tasks for all test artifacts. If you use Insight, you must download and replace all xdc files, the Reporting Data Model, and the Data Manager package with the artifacts from this release.

    NOTE: Data migration is not included in this milestone release. You can continue using the data in a non-migrated state or run a Full Load of your ETLs migrate it.

  • A new report management page was added that uses a design that is consistent with the user experience in Rational Team Concert. For example, the page includes separate pages for shared and private reports, reports that use templates in special editor pages, multi-report operations (for example, move many reports at the same time), the ability to create your own custom report folders, search for reports, and manage report templates.

Test execution

  • The new Assisted Manual Testing feature is a new integration between Rational Functional Tester and Rational Quality Manager. When enabled, you can use the manual test script recorder to create a manual test script in Rational Quality Manager to test an HTML application. You must install the Rational Functional Tester version 8.2.2 Beta to use this feature (work item 52828). For more information, see the Configuring the manual test script recorder help topic in the information center.
  • Support was added for execution of Selenium and JUnit tests integrated with RQM (work item 52748).
  • You can initiate an RQM script or test suite execution from the command-line with the new RQM Command-line Execution tool (work item 39955). For more information on the new tool see this wiki page: https://jazz.net/wiki/bin/view/Main/RQMExecutionTool.
  • A new Execution Record Queries widget was added to provide links and summary information to commonly used queries (work item 57936).
  • You can now include defect and build information when creating execution records in bulk (work item 58522).
  • A new execution project preference was added to control search behavior for finding test automation adapters to run automated tests based on the execution records test environment (work item 55376).
  • PermFailed and Deferred step verdicts were added for manual tests and their associated weight distribution sliders are included in execution results (work item 28534).
  • You can now change owners with bulk owner change support in the Execution Console view and view additional columns in the Execution Console view (work item 57727 and work item 57729).
  • You can skip execution of a selected test case when running a test suite. This allows you to rerun only the test cases that did not pass during a previous test suite execution (work item 54169 and work item 57578).
  • Testers can now update the estimate and time spent fields of an execution record on the Manual Script Execution page while executing the script. (work item 59346)
  • The project properties for only allowing execution of approved test cases and approved test suites have moved to the project process specification. Also, a new process operation was added to restrict the execution of approved test scripts only (work item 53119 and work item 54640).
  • You can now associate a test suite with a test cell (used for test suites associated with automated scripts). This allows users to select a test cell for the automated scripts to be distributed to during test suite execution (work item 58381).

User assistance

Help for deploying a clustered environment

The following new topics describe how to configure and deploy a cluster of servers to achieve load-balancing and high availability by using WebSphere Application Server Network Deployment:

The interactive installation guide has also been updated to include a choice for clustering:

A screen capture of the part of the interactive installation guide that lets users specify a clustered environment

Interactive upgrade guide updated for 4.0

The interactive upgrade guide has been updated to describe how to upgrade to the 4.0 release:

Help for setting up the server and applications via the command-line interface

As an alternative to using the Setup Wizard, you can now set up the Jazz Team Server and associated applications by using the command-line interface.  The Running the setup with command-line commands topic describes how to do it.

Help for using Jython scripts to set up WebSphere Application Server and deploy CLM applications

See the Setup WebSphere Application Server and deploy CLM applications using Jython scripts topic for details about how to use Jython scripts to automate common administration tasks and configure security in WebSphere Application Server.

Content filtering in the information center

Help content filtering is now available in the Rational solution for Collaborative Lifecycle Management 4.0 information center. By setting a filter, you customize the online help to suit your information needs. At any time, you can modify the filter to see fewer or more topics. Alternatively, you can remove the filter to see all the help topics. The filter affects the topics that are listed in both the navigation tree and the search results.

To access the filter options, click the Filter icon in the information center banner:

Help filter icon

The filter dialog opens and you can choose to filter content by role and capability:

Help filter dialog

For more information, see Filtering the help.

M7 task guide

For more information about the updates available in M7, see the M7 task guide for further background and step-by-step instructions on the new features.


New & Noteworthy in RQM 3.5 M5

Integrations and requirements

  • Simplified import of requirements via Excel. The requirements are now imported directly into RRC without passing through the RQM REST API. The RM credentials can now be provided on demand instead of being stored in the Advanced Properties page of the administration console.
  • Requirements can now be linked directly to steps in manual test scripts.
  • Hierarchical categories can now be imported via the Word or Excel tool.
  • When reconciling requirements you can now create a quality task work item directly from the Reconcile dialog box.

Test execution

  • A Priority field has been added to Test Case, Test Suite, Test Case Execution Records and Test Suite Execution records to allow prioritization of test activities.
  • Estimate and time spent fields have been added to execution records to allow tracking of the time required for test activities.
  • Custom attributes, editors and hover help have been added to test case and test suite execution records.
  • Execution status bars are shown in Test Case Execution Record and Test Suite Execution Record views when grouping execution records by owner.
  • A new Execution Records viewlet shows execution records in the dashboard based on user defined query parameters.
  • A new Execution Status viewlet shows execution status bars for execution records owned by testers.
  • Test suites can now execute test cases that do not have test scripts associated with them.
  • You can now assign an owner to the steps of a test suite, in order to better support sharing execution of a test suite between multiple testers.
  • The test suite results table and editor page shows flat counts for the number of test cases passed, failed, or blocked that are part of the test suite.
  • Test case pre-conditions and post-conditions are now displayed on the manual script execution page.
  • You can now bulk update the build associated with test case and test suite results.
  • More options are available when generating test case results in bulk via the create result without executing option.  This includes the ability to add notes, set the weight distribution, custom attribute and category information for the generated results.
  • A custom adapter search option has been added when selecting which adapter to run an automated test on.  This allows for environment information in the execution record to be matched against attributes defined in the lab resources where the adapters are running.
  • Using the command line adapter, you can now attach files and links to execution results. For more details, see Add simple "attached files" support for command line adapter execution results (52885).

General UI improvements

The QM menus are updated to align with the CLM capability menus standard. Instead of grouping the menu items by artifact types (such as Test Case, Test Script, and so on in the Construction menu), they are now grouped by action (Browse, Create, Import, etc). Promoted saved queries are now in the new Browse My Queries and Browse Shared Queries menu item groups instead of a pull-right sub-menu off the View <artifacts> menu item. There are new menu item groups for Recently Viewed, Unsaved Artifacts and Recent Queries. These menu item groups provide the same capability as the tabs in QM to bring up the already opened pages.

M5 task guide

For more information about the updates available in M5, see the M5 task guide for further background and step-by-step instructions on the new features.


New & Noteworthy in RQM 3.5 M3

Requirements: DOORS/RQM integration using OSLC

In M3, you can integrate DOORS and RQM using OSLC. To set this up, do the following:

  1. Add DOORS as a friend in the Jazz Team Server Administration page.
  2. Add DOORS as the Requirements Management (RM) provider for the RQM project.
  3. Associate an RQM test plan with the DOORS requirement view.
  4. Add a bi-directional link between an RQM test case and a DOORS requirement.

For more details, see [QM] RQM/Doors Integration - bi-directional link between RQM and Doors (54712).

CSV Export of data in table views

It is now possible to export data in the following table views to CSV format, where the data can later be reused; Test Plans, Test Cases, Test Scripts, Test Suites, Test Case Execution Records, Test Suite Execution Records, Test Case Results, and Test Suite Results. See CSV Export for table view data.

Test execution

General UI improvements

Improvements to the RQM Reportable REST API


New & Noteworthy in RQM 3.5 M1

Improved requirements capabilities

  • Rich hovers are now provided for Rational RequisitePro requirements. The rich hover shows all of the information that is provided by RequisitePro, including the RequisitePro project, the content (tag, name, text, package, and so on), and a link to the RequisitePro requirement or view.

    Rich hovers for RequisitePro

  • Integrated RequisitePro requirements can now be migrated to Rational Requirements Composer.
  • The user experience has been improved for reconciling requirement suspect status.
  • It is now possible to exclude specific requirements from migration to Rational Requirements Composer.
  • Improvements have been made to the DOORS integration.

Improvements to the RQM Reportable REST API

Performance improvements

Both the Adapter and Execution consoles now support paging.

Execution enhancements

The following new options are now available for weight and verdict roll-up when modifying test case results that are part of a test suite result:

  • You can now set the Update Test Suite Result points and verdict when Test Case Result is modified execution preference to control whether or not the verdict and weight changes in a test case result are automatically rolled-up to the test suite result.
  • From a test suite result, you can click the Calculate weight icon to update the weight of a test suite result to reflect the weights of the test case execution results created during test suite execution.
  • Test case results now include a Related Suite Result panel.

You can now link test suite results to build records.

Users are now required to enter values for required custom attributes before closing manual script execution results.

Automatic unblocking of test case execution records when a ClearQuest defect is resolved

The Rational Quality Manager integration with ClearQuest now supports automatic unblocking of test case execution records when a blocking ClearQuest defect is resolved. When you configure automatic unblocking, the change management integration service runs at a selected interval and checks for blocking defects that have been resolved. To use this feature, you must be using ClearQuest version 7.1.2.2 or later with the OSLCLinks package version 1.2. Follow these instructions to configure the change management integration service:

  1. Click Admin > Manage Application.
  2. Under Configuration, click the Advanced Properties section.
  3. Scroll to the RQM Change Management Integration section and click Edit.
  4. Enter a user name and password for ClearQuest.
  5. For Delay, type a value, in seconds, for the interval at which you want the change management integration service to run. The default value is 500 seconds.