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 Release Candidate 0 (Beta) Milestone

Early Access Milestone | March 6, 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 RC0 (Beta) New And Noteworthy

Rational Quality Manager 4.0 RC0 (Beta) New and Noteworthy

Here are some of the most noteworthy items in Rational Quality Manager 4.0 RC0.

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 RC0 (Beta) 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 RC0 (Beta) and Rational Requirements Composer 4.0 RC0 (Beta).

Table of contents

See the New & Noteworthy information for previous milestones:


Clustering for High Availability

Clustering provides high availability with automatic failover. While we have delivered clustering functionality in this milestone, we are still working on improving the ease of installation, setup and configuration for a clustered deployment. Consult the latest instructions to find out how to obtain the necessary supporting programs and deploy CLM in a cluster.


Server rename

In this milestone it is now possible to change the public URLs of one or more of the servers or applications in your deployment. In previous releases, changing a public URL after deployment was not possible. While planning a deployment and choosing stable URLs is still highly encouraged, there are some situations which require a URL change because other techniques for preserving URLs (e.g., DNS, reverse proxy, etc.) will not suffice. For example: cross geography relocation, reorganization/acquisition, dropping domain name, data center consolidation, alignment with corporate naming policies, etc.

The server rename feature is not yet complete and we are still working on improving the ease of performing this operation including the impact on any products that might integrate with renamed servers. As this feature is being constantly improved you should consult the latest instructions. If you require assistance, please contact us via e-mail and include information about your current deployment (e.g. installed products, topology, operating system, application server, and database sizes).


Construction

Manual test script recorder

The new manual test script recorder feature is an 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 2 to use this feature.

The manual test script recorder is an integration catering to the needs of an author of manual tests. Using this capability, you can now record the user gestures made on the application and they are converted to manual script statements in the English language. While doing so, the application screen shots are automatically captured as well, highlighting the area you interacted with. You can create a new manual script, insert steps into existing via recording, and create a manual script from test case design sections to get that manual script linked to the test case.

In Rational Quality Manager 4.0 RC0 and Rational Functional Tester 8.2.2 Beta 2, this support is extended for applications built using HTML, Dojo (limited support), and Java (limited support). These scripts can then be saved in Rational Quality Manager to run manually.

For more information, see the help topic Configuring the manual test script recorder in the information center.

CSV export

CSV export has been moved to the print framework in M7. Basically, this means you can access your CSVs in the Print Queue, as you do with the PDFs you generate. As of RC0, many of the table artifact views (Planning > Browse > Browse Test Plans or Construction > Browse > Test Cases), can now be exported as a .csv file for spreadsheet use. What you see in the UI is what you get in the resulting CSV file, including selected columns, sorting, and filtering. If the table view contains multiple pages, all are exported. The resulting CSV files are queued and processed in the same manner as printing PDFs are, so you must go to the Manage Print Job Queue to download the finished results.

There is a known bug which causes the specified sorting and filtering to occasionally be ignored, see work item 62501. The following screen capture shows the new Download as spreadsheet button.

Test case screen shot showing the Download as spreadsheet button.

E-Signature

Operations requiring an E-Signature are now enabled through Process Configuration.

Formal Review

The Formal Review presentation and functionality has been improved with the following features:

  • Improved look and feel
  • Formal review support has been added to Test Scripts, Test Case Results, and Test Suite Results
  • Assign multiple reviewers

    Shows the new Formal Review section.

  • Organize review and approval using groups
  • Display multiple comments per group and general approval comments
  • Allow to approve or reject for read-only or locked artifacts
  • Added time for due date approval
  • Allow @ user mentions in comments
  • Batch approve test plans, test cases, and test suites

    Image shows the pop-up menu for approving multiple selected reviews.


Dashboards

Prior to Rational Quality Manager V4.0, dashboards were personal dashboards in the quality manager application scope. The default process template has only a personal dashboard template and the personal dashboard permission defined. After migration to V4.0, the personal dashboards are accessed through the Home menu and are managed by JTS.

There are a few issues with the existing project process: (Work item 62140)

  • When creating new personal dashbaords in JTS, the old personal dashboard template is used.
  • The Rational Quality Manager home page is the generic project dashboard.
  • Only the personal dashboard permission is defined in the process, so the project dashboard is read-only.

These issues will be addressed in a future V4.0 milestone.

Work around:

To work around missing permissions to edit Team and Project dashboards in a migrated project, manually set the Save Team and Project Dashboards permission in the project area.


Integrations

Rational Publishing Engine (RPE) and Rational Reporting for Document Generation (RRDG)

RPE templates can now be added to, and executed from, the common reporting UI.  Some sample templates are available which demonstrate how to compose RPE reports for use in this way. (work item 56643)

For more information, see Creating a document-style report in Rational Publishing Engine using Collaborative Lifecycle Management application data in the information center.

DOORS 9.4 and Rational Quality Manager 4.0 OSLC V2 integration

New features in M8 and RC0

The following functionality is now available:

  • Associate a DOORS module or view to a test plan
  • Create new or add existing DOORS requirements to a test case
  • Reconcile requirements and collections
  • Generate test cases
  • Accept changes and suspect test cases

The following screen capture shows the first step in associating a DOORS module to a test plan.

Add a requirement collection dialog box.

Integration versions and reporting

If you integrate Rational Quality Manager V4.0 with Rational DOORS V9.4 using OSLC, you must open Rational Insight to run Data Manager ETL before you can use the out-of-the-box BIRT or Cognos-based reports for requirements.

Supported service provider type

For RC0, the only supported service provider type is Services for DOORS ERS Repository.

For DOORs 9.4.*, one DOORs server provides several Requirement Service Providers: one service provider for Services for DOORS ERS Repository and several (or none) service providers for each view and module. These service providers are categorized under the entry Service Provider Catalog; the service provider name is the corresponding view or module's name in DOORs. The following screenshot shows an example:

Service provider selection dialog box.

If you select Services for DOORS ERS Repository as the service provider, you will be able to add any module or view in the current DOORS server as requirement collection to Rational Quality Manager test plan and any requirements in the current DOORS server to Rational Quality Manager test case or test script.

If you select the service provider under Service Provider Catalog, you can only add the corresponding view or module and it's child view or modules to a test plan, and requirements under the corresponding module or view to test case/test script. However, as DOORS has not completed this expected feature, in the current dialog box, you will see the same behavior as what you get from a "Services for DOORS ERS Repository" service provider. This is not an expected behavior, and might cause unexpected failures such as reconcile failures. Please do not use this type of service provider in the current release.

DOORS does not support "Create Requirement Collection"

Because DOORS V9.4 does not provide the "Create Requirement Collection" service, you cannot create a DOORS requirement collection from Rational Quality Manager. The following areas are affected:

  • In a test plan, if you attempt to add a Requirement Collection Link, you will receive a message indicated that "the requirements provider does not support this operation."
  • In the Requirements menu, under Services for DOORS, Create Requirement Collection is not supported.

Requirements menu view.

DOORS V9.4 and Rational Quality Manager links can be inconsistent

In the DOORS application, a DOORS requirement or requirement collection can create a ValidateBy link to an Rational Quality Manager artifact, such as a test case, test result, test script, or test plan. But in Rational Quality Manager, only a test plan can be associated with a requirement collection. Test cases and test scripts can be associated with individual requirements. The unsupported link relationship is not shown in Rational Quality Manager. (work item 61618)

Troubleshooting the DOORS integration

If you see the following error message: "No requirement management provider configured, please consult your administrator for more details," it is related to the incorrect configuration of DWA communication to the DOORS database. Configure the following properties:

  • dwaProtocol set to https
  • dwaHost set to DWAserver (use the same hostname as you have set in RQM as friend)
  • dwaPort set to 8443

For complete information on how to correctly configure communication, see the DWA help in the Rational DOORS information center.


Planning

Project templates

This milestone introduces the ability to create templates of project areas. You can extract a process template from an existing project area that includes a specific Rational Quality Manager project configuration, such as custom attributes, artifact categories, and UI templates. This can be done in the Rational Team Concert client using the Extract Process Template context menu command on a connected project area.


Requirements

Requirement traceability to test script step

You can now associate requirements to test script steps, allowing improved traceability and better impact analysis. The following functionality is new for RC0:

  • Set project preferences for test script linking and propagation of new requirement links to the parent test case
  • Drag and drop individual requirements that are associated with the parent test case to a test script step
  • View requirement associations during test case with scripts execution

Known issues:

  • Remove requirements from test script step will not auto refresh the validate links column, need a manual refresh (62469)
  • The requirement is sometime not added to the expected step when drag from Requirement View (63367)

Hide requirement risk information from UI and REST service

A preference has been added to turn on legacy requirement risk support. By default, all requirement management functionality is provided in Rational Requirement Composer, including any custom attributes used for risk management.

To use the requirement risk feature, on the Application Administration, Advanced Properties preferences page, in the Requirement section, set Display legacy risk information to True.

New wizard for requirement reconciliation

In a test plan, in the Requirement Collection Links section, you can click the Reconcile all the requirement collections button to open a wizard that guides you through the reconciliation of requirements that are associated with the test plan and do not have test case coverage. Follow the instructions in the wizard pages to select requirements to add to existing or new test cases and to optionally mark corresponding test cases as suspect to reflect the changes.

The following screen capture shows a page of the new wizard.

Grouping Rational RequisitePro views and packages by server and project

When viewing requirement collections in the Requirement Collection Links section of a test plan, it is now easier to distinguish between a package, view, or requirement in one Rational RequisitePro project from a similarly named package, view, or requirement in a different Rational RequisitePro project.

The Requirement Collection Links section with Group By field set to Project Name.


Reporting

BIRT reports

Five new BIRT reports are available:

  • Test Artifacts States
  • Test Scripts by Development State
  • Test Suites by Development State
  • Test Case Coverage by TER
  • Test Case Coverage by Test Script

Test Artifacts States

Test Artifacts States is a chart-based report that shows counts of Test Cases, Test Scripts, and Test Suites by their state, such as Draft and Under Review.

Test Scripts by Development State

Test Scripts by Development State is a tabular report listing Test Scripts and their state, such as Draft and Approved.

Test Suites by Development State

Test Suites by Development State is a tabular report listing Test Suites and their state, such as Draft and Approved.

Test Case Coverage by TER

Test Case Coverage by TER is a chart based report that shows the counts of TERs and their states by Test Case.

Test Case Coverage by Test Script

Test Case Coverage by Test Script is a chart based report that shows the number of Test Scripts that are associated with Test Cases.

Cognos reports

"Points PermFailed" and "Points Deferred" from the test execution results have been added into out of the box Cognos-based reports that are related to execution weight to match the productizing SVT's reporting customizations. (task-development item 59849).

Nine new Cognos-based reports are available:

  • Execution Result Date Metrics
  • Execution Result Metrics
  • Execution Result Metrics with Iteration
  • Execution Result Points Metrics with Iteration
  • Execution Work Item Metrics with Iteration
  • Project Test Case Metrics with Test Plan
  • Request Metrics with Test Plan
  • Test Suite Execution Summary
  • TSER Status using Weight

Execution Result Date Metrics

Execution Result Date Metrics is a metric report that shows the monthly trend of test execution results and points for the selected project, Test Plans and Test Cases. The graphs show the monthly trends of points and the table provides a summary of execution results and the associated points.

Execution Result Metrics

Execution Result Metrics is metrics report that shows the test results of all test executions for the selected project, Test Plans and Test Cases. The graph shows the count of execution results verdicts for each Test Plan and the table shows execution result verdicts by Test Plan and Test Case.

Execution Result Metrics with Iteration

Execution Result Metrics with Iteration is metrics report that shows the test results of all test executions for the selected project, Test Plans, Test Cases and iterations. The graph and cross tab show the count of execution results verdicts for each Test Plan and Iteration.

Execution Result Points Metrics with Iteration

Execution Result Points Metrics with Iteration is metrics report that shows the test execution results and the total points that are attempted, blocked, failed, inconclusive, and passed for the selected project, test plans and iterations. The two graphs respectively show the count of execution results and execution result points for each Test Plan and Iteration.

Execution Work Item Metrics with Iteration

Execution Work Item Metrics with Iteration is metrics report that shows the owner wise allocation of execution work items and their weight for the selected project, Test Plans and iterations. The graph shows the count of TERs assigned to each owner.

Project Test Case Metrics with Test Plan

Project Test Case Metrics with Test Plan is metrics report that shows the owner wise distribution of Test Cases and their states for the selected project and Test Plans. The graph shows the state wise count of Test Cases for a project.

Request Metrics with Test Plan

Request Metrics with Test Plan is metrics report that shows the defect states by Test Plan. The graph shows the count of defect states for a Test Plan and Iterations.

Test Suite Execution Summary

Test Suite Execution Summary is a tabular report summarizing the planning status and execution status of test suites. See TestSuiteExecutionSummary.png

TSER Status using Weight

TSER Status using Weight is a chart based report that shows the execution status by test suite execution records in a specified test plan, measured against weight. It could be drill-through from Execution Status by Test Suite using Weight report.



Test execution

  • Support to include built-in execution variables, which are used to pass automated script contextual information about the run being executed. This includes information such as the test case, test plan, and test execution record being executed. (work item  35822)
  • Ability to associate a favorite adapter to use when executing automated test scripts. (work item 58273 )
  • Add process advisor support to require at least one work item be associated with any failed execution results before submitting them to be reviewed. (work item 61310 )
  • Run Test Case and Run Test Suite dialogs now allow you to specify a future date for which you would like to start automated test executions. (work item 16622)
  • A user preference has been added to automatically close results once a run has completed, returning you to the page you where on before starting the run. (work item 56640)
  • You can now search execution records associated for the current iteration, as specified in your project timeline. (work item 52701 )
  • Test artifact priority is now customizable via the project properties.
  • Additional information of a execution records last result, such as points passed/failed, has been added to the Test Case and Test Suite Execution records table. (work item 40762 )

Traceability and live views

  • Execution and traceability dashboard viewlets (work item 59534 )
    • Test plans traceability links
    • Test cases traceability links
    • Test suites execution status

  • Traceability Views in execution record & result tables (work item 60336 )
    • Test case execution record and result tables: related defect links
    • Test suite execution record and result tables: related defect links


User experience fixes and enhancements

  • Many tables now support a row action menu. In the test artifact tables, the actions that can be taken on rows of the table have been moved to a pop-up menu that opens when you click a button with a pencil icon, which is located in the column to the right of the selection check box. (work item 61237 )

  • Allow project admins to define project wide default display settings for View artifacts tables (work item 60828 )

  • Show test case/suite execution records in sections in the test plan editor (work item 42124 )

  • Refresh action to reload the artifact content in test plan, test case, test suite, test script editors (work item 59462 )

  • String type custom attributes now can be sorted in artifact tables (work item 58971)
  • You can now hover over images in the Rich Text fields and the full image preview will be shown (work item 58963 )
  • PDF Export now respects user's column selection and sizing preferences on most tables (work item 55824 )


RC0 task guide

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