Download 6.0.6.1 Release
April 23, 2019
Try
Buy

IBM Rational Quality Manager

Quality management · Manual testing · Continuous improvement

Rational Quality Manager 4.0

Product Release / Trial | June 12, 2012
This is not the most recent version. We recommend Rational Quality Manager 6.0.6.1 . 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.

Rational Quality Manager 4.0 New And Noteworthy

Rational Quality Manager 4.0 New and Noteworthy

This is a summary of the main new features and improvements in the 4.0 release of Rational Quality Manager.

Rational Quality Manager is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM), which provides seamless integrations for application lifecycle management with reduced cost of ownership and administration, improved cross-product visibility and reporting, and lifecycle integrations.

For information about new features and changes in other parts of the Rational solution for CLM, see the Jazz Foundation 4.0 "New and Noteworthy", the Rational Team Concert 4.0 "New and Noteworthy", and the Rational Requirements Composer 4.0 "New and Noteworthy".

Table of contents

Clustering for high availability
Server rename
Test planning Manual test recorder
Test execution Team collaboration and process configuration Integrations Requirements User experience enhancements CSV export
Changes to the RQM Reportable REST API
Dashboards
Reporting

Clustering for high availability

Clustering provides high availability with automatic failover. To find out how to obtain the necessary supporting programs for clustering and how to deploy the Rational solution for CLM in a cluster, see the High Availability with Rational solution for CLM 2012 Clustering article on jazz.net and the Setting up a clustered environment infocenter topic.


Server rename

In V4.0, you can 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, such as DNS and reverse proxy, are not sufficient. For example, these situations likely require a URL change:

  • Cross-geography relocation
  • Reorganization
  • Acquisition
  • Dropping a domain name
  • Data center consolidation
  • Alignment with corporate naming policies

For additional information on server rename, please see the Changing the public URL using server rename infocenter topic and the related jazz.net article.


Test planning

Test prioritization helpers

New fields are available for test artifacts to help you plan and track testing activities. These enhancements allow you to tackle the top priority tests first and find critical defects early. Estimate and priority fields have been added to test suites, test cases, and test execution records.

Priority is customizable via the project area administration page.

A time spent field has been added to test case and test suite execution records and status bars are provided in several areas of the UI to display test progress.


Execution progress views

Execution progress views allow you to track and optimize test execution in real-time.

Here is an execution progress view in an individual test plan:

Here is an execution progress view in a list of test plans:

There is also a test plan execution status dashboard widget.


Traceability views

Traceability views are available that help to identify gaps and analyze the impact with lifecycle traceability. There are views that show links between several artifact types, for example:

  • From test plans to requirement collections and development plans
  • From test cases to requirements and development work items
  • From test scripts to requirements
  • From test suite/case execution records (TERs) and results views to defects

Traceability Views are available in execution record result tables:

  • Test case execution record and result tables: related defect links
  • Test suite execution record and result tables: related defect links

There is PDF Export support for Traceability and Live Views.


Test construction using the manual test recorder

The new manual test recorder is an integration between Rational Functional Tester 8.2.2 and Rational Quality Manager. When enabled, you can use the recorder to create a manual test script in Rational Quality Manager to test an HTML application, a Java application, or an applications with Dojo controls.

Using this feature, you can record user gestures, which are then converted to English-language manual script statements. The manual test script recorder also automatically captures screenshots of the application where the gestures were made.

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


Test execution

Test execution adapters

This release provides support for developer testing of the Web UI through the JUnit Selenium adapter. This support lets you run Selenium version 2.0 WebDriver JUnit4 tests in the Quality Management application. Selenium automates browsers, primarily for automating web applications for testing purposes.

The command-line adapter has been improved to allow association of user defined files and links to the RQM execution results produced by command-line scripts.

This release also includes several improvements related to selection of test adapters to execute automated tests, including smarter distribution of adapters across a pool of test machines executing automated test suites. RQM can now match information about the machine running the adapter, such as the OS, against information in the test execution record being run.


Jazz process support

Execution preconditions, such as "Only allow execution of approved test cases", are now implemented using the Jazz process. Several new preconditions have been defined, such as requiring build information to be provided when a run starts and requiring at least one work item to be associated with any failed execution results before submitting them to be reviewed.

In addition, test case preconditions and follow up actions are now displayed on the manual script execution page.


Ability to schedule jobs

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. The scheduled executions can be managed by the new Execution -> Scheduled Jobs view.


New editor for execution records

An editor has been added for execution records. This allows information pertaining to the execution record to be modified from a single location. In addition, custom attributes have been added to execution records.


New dashboard widgets

Several dashboard widgets are now available that focus on execution records and test status. These include the Execution Record(s) and Execution Records Queries widget, the Team Execution Status for Test Cases widget, and the Team Execution Status for Test Suites widget.


Test suite improvements

Several improvements have been made for test suites, including:

  • You can assign an execution owner for each step in the test suite to allow multiple testers to run the suite simultaneously.
  • Test suites can now execute scriptless test cases.
  • You can utilize distributed automated testing using test cells.
  • There are now rich hovers for test suites and related artifacts.
  • Test suite results and related tables can now show flat test case counts (# passed/failed/in-progress test cases)
  • You can now run test suites with only selective test cases.

This image shows the Run Test Suite dialog where several scripts within the suite have been marked to skip during execution:


Improvements for recording test results without execution

These improvements allow the user to specify information such as notes, defects, build information and more when recording execution results in bulk.


Miscellaneous improvements

  • Support for 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.
  • 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.
  • You can now search execution records associated with the current iteration, as specified in your project timeline. This allows shared queries to be defined for the execution records for the current user in the current iteration, allowing each tester to more easily focus on their daily tasks.
  • Additional information about an execution record's last result, such as points passed or failed and completion time of last result, has been added to the Test Case and Test Suite Execution records table. These are queryable and sortable, allowing you to construct queries that show you the execution records with the highest number of failed points or the execution records that where completed in the last 24 hours.
  • 4.0 introduces the new RQM Execution Utility which is a stand-alone application used to execute Test Case and Test Suite Execution Records. This tool allows users to execute tests from the command-line for integration between RQM and external test automation frameworks. For more information see the RQM Execution Utility wiki page.
  • Permanently Failed and Deferred step verdicts have been added for manual tests
  • There are additional columns in the Execution Console view, including execution request owner, suite progress, test plan, iteration and others.

Team collaboration and process configuration

You now have much greater control over the process that governs your Quality Manager projects.


Support for timelines, iterations, and team areas

You can now create project area timelines that support test iterations across test plans and create test schedules that are associated with these timelines. There is a notion of "current iteration" in the timeline that can be used to drive views, queries, and dashboards.

You can assign test artifact ownership to team areas and use team areas to configure team-specific process, permissions, and timelines for the team's test artifacts.

Role-based permissions are now (optionally) defined at the team level. This provides flexibility in configuring different permission sets for different teams, giving you the ability to segment a project's users into groups.

Operation advisors in the form of preconditions (for example, "not allowing execution of test assets that are not approved") are configurable directly in the process specification and can apply at the team level. For further details, see Timelines and Iterations in Rational Quality Manager


Enhanced review and approval process

The review and approval process has been improved with several new features and helps you achieve higher quality through online, in-context feedback.

  • Improved look and feel
  • Available for test plans, test suites, test cases, test scripts, test suite results, and test case results
  • Support for multiple reviews and approvals

    Shows the new Formal Review section.

  • Test artifact state transition can be linked to approval using operation behaviors
  • Ability to set up groups when organizing review and approval
  • Ability to display multiple comments per group and general approval comments
  • Ability to approve or reject for read-only or locked artifacts
  • Added time for due date approval
  • Ability to mention users in comments using the "@" symbol
  • Batch approve test plans, test cases, and test suites

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


E-Signature

Enhanced E-signature support is available to help you comply with regulatory requirements. Operations requiring an E-Signature are now enabled through process configuration.

  • Used in artifact locking and unlocking and review and approval
  • Ability to sign multiple artifacts at once
  • History shows who signed, when, for what action, and comments
  • Configured using the Rational Team Concert client

Process templates

Using the Rational Team Concert client, you can now extract a process template from an existing QM project area, allowing you to reuse best practices and quickly setup new projects. A QM process template can include the following:

  • Roles and permissions
  • Test artifact workflow customization
  • Test artifacts templates
  • QM project properties and preferences such as custom attributes, artifact categories, UI templates, and quality objectives


Test artifact workflow customization

You can now customize the workflow for several test artifact types, including test plans, test cases, test scripts, test suites, and test execution results. All workflows are defined at the project level.

  • Each artifact type comes with a predefined set of state transitions, which can be customized.
  • Each artifact supports a set of pre-defined state groups, which can be used to write process enforcement against.
  • Each state will then map to each state group.
  • Transition between states can be customized.
  • You can assign process advisers on each state that act as preconditions or follow-up actions using the Rational Team Concert client.


Integrations

DOORS 9.4 and Rational Quality Manager 4.0 OSLC V2 integration

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.


Requirements

Requirement traceability to test script step

You can now associate requirements to test script steps, allowing for improved traceability and better impact analysis. With this feature, you can:

  • 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

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.


Improved 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.


Rich hovers for Rational RequisitePro requirements

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


User experience

>Changes to the default QM browsing experience

In 4.0, the default QM browsing experience no longer includes tabs. There are many features that make this browsing experience beneficial while adding more screen space. Of note, you will see your recently accessed test artifacts and queries listed in the menus to make accessing them easy. You will also find the back button useful for navigating to a recently accessed item. Finally, if you prefer to return to the old UI with tabs, just click My Preferences for Quality Management, select Page Tabs Layout, and deselect Do not use tabs in the page layout.

Preferences - Page Tabs Layout.


Defect menu is now the Change Requests menu

Users access CCM from QM to work with different work item types and not just defects. Therefore, we have renamed the menu item to refer to "Change Requests" instead of "Defects". The functionality is the same as it was before.

Menu name changed from Defects to Change Requests

Row action menu in tables

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.


Project wide display settings for tables

Project administrators can now define project wide default display settings for test artifact tables.


Images in rich text fields

You can now hover over images in rich text fields and the full image preview will be shown.


CSV export

Many table artifact views can now be exported as a .csv file for spreadsheet use. With CSV export you can access your CSVs in the Export Job Queue, as you do with PDFs that you generate. 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 exporting PDFs, so you must go to the Manage Export Job Queue to download the finished results.

The following screen capture shows the new Download as spreadsheet button.

Test case screen shot showing the Download as spreadsheet button.


Changes to the RQM Reportable REST API

The RQM Reportable REST API has evolved in RQM 4.0. For more information on the notable changes and improvements see Notable changes from RQM 3.x.


Dashboards

QM now supports project and team dashboards. When logging in to QM, you will see the project dashboard. A default project dashboard template is provided with interesting content that can be customized based on your project's needs. Prior to version 4, dashboards were personal dashboards scoped to the Quality Manager application. The default process template had only a personal dashboard template and the personal dashboard permission defined. After migration to version 4, personal dashboards are accessed through the Home menu and are managed by the Jazz Team Server. Remember that permissions to modify the project dashboard are separate from those used to manage your personal dashboard.


Reporting

  • New consistent report management UI for CLM
  • Readability and printability improvements for BIRT reports
  • New BIRT reports for test preparation and test suite execution
  • New Cognos report designs and custom report templates
  • New Cognos reference reports to kick-start custom reporting
  • Support for document style reports with IBM Rational Publishing Engine
  • New reportable data
  • Data Manager ETL performance improvements and optimizations
  • New enablement videos

New consistent report management UI for CLM

In 4.0, the reporting user interface has been improved and updated to be common across CLM applications. There is a Shared Reports View that shows all reports shared across the project. This view includes the ability to create new folders for reports. Users can also create reports from report resources, import reports, delete reports, and copy or move reports to other folders.

There is a similar view, called My Reports, that shows reports that are private to the user. This view has all the same actions as the Shared Reports view.

Also new in 4.0 is the ability to access the Report Resources (formerly known as Report Templates) within the QM application. Previously, access to Report Resources required the Rational Team Concert client. Users can deploy new reports or update the report resources for existing reports directly from this view.


Readability and Printability improvements for BIRT reports

Chart-based reports now include a table at the bottom of the report that shows the details of the report data to make the reports more readable and understandable, especially when printed.

All reports now include a collapsible section that shows the parameter values selected for the report. These sections are expanded when you print the report to ensure that the information is available in the print-out.


New BIRT reports for test preparation and test suite execution

The following new 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
  • 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

For example, here is the Test Artifacts States report, which 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.


New Cognos report designs and custom report templates

All Cognos reports now use a new set of styles and new layout to improve usability, readability, and printability of the reports. These styles (called RATL_ styles) are also available to authors of custom reports as well as to all new report templates for creating custom full page and viewlet mini reports using Report Studio. When you log on to Cognos Connections, you will find these templates in Public Folder > Report Templates. The templates are named RATL Report Template and Mini RATL Report Template.


New Cognos sample reports for reporting on metrics and execution results

  • 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

For example, here is the Execution Result Metrics report, which shows the test results of all test executions for the selected project. 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.


New Cognos reference reports to kick-start custom reporting

This release adds a new set of reference reports, which are prefabricated report samples that are intended to be used as a starting point for authoring your own custom reports. Use these reports to create metric reports using different types of graphs, such as Line, Bar, or Table-based reports for full page report displays or viewlets that can be shown in a CLM dashboard. You can find the new reports in the public RRDI/Insight connections folder 'Sample Report Definitions > QM > Reference Reports'. The new reports are as follows:

  • Mini Report - Bar Graph - Defect Arrival and Resolution
  • Mini Report - Bar Graph - Execution Points Over Time
  • Mini Report - Line Graph - Defect Arrival and Resolution
  • Mini Report - Table - Execution Results
  • Report - Bar Graph - Execution Points Over Time
  • Report - Line Graph - Execution Points Over Time
  • Report - Metrics Table - Execution Result Metrics With Iteration
  • Report - ODS Table - Execution Result Related Requests

Support for document style reports with IBM Rational Publishing Engine

You now have the option to build completely customized document-style reports thanks to a new level of integration between RQM and Rational Publishing Engine (RPE). After creating a report template in RPE's Document Studio, you can upload the template from the Reports menu in RQM and create reports based on that template. You can run these reports from RQM's Web UI like any other report.

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


New Reportable Data

This RQM release provides various new capabilities, which have also been made available for your custom reports. We also addressed feedback from RQM users who wanted full coverage for reporting of custom attributes and categories. Here is the list of data items that are now available for custom reporting using Report Studio or Query Studio:

"Points PermFailed" and "Points Deferred" from the test execution results have been added to all out-of-the-box reports (BIRT and Cognos) that show results based on execution weight.

  • All categories
  • All custom attributes
  • Custom artifact states and state groups for cross-process reports
  • Execution result permfailed, deferred, and total points
  • Quality task
  • Phase descriptions

Other key Rational Team Concert and CLM enhancements that are important for Rational Quality Manager reports include:

  • Work Item Due Date and Creator (also creator dimension for Request metrics)
  • CLM link types
  • Many metrics fixes

Data Manager ETL performance improvements and optimizations

For Rational Insight users, there is a new XDC file that enables performance improvements for customers with a large number of projects. You can find this alternative XDC file, called "rqm40-cross-project-etl-alternative.xdc", in the Reports > Download administration page. You can use this XDC file instead of the default rqm40.xdc file if you have a large number of project areas on your RQM server. We also provide a migration job if you used the rqm40.xdc (and/or the 3.0.1.x equivalent files) first. You can find the job in RQM4_Jobs > RQM4_MigrationsJobs called RQM_Migrate_to_XProjETL_4.0.

The default XDC file causes the ETLs to iterate over each project on the server one by one, thus retrieving resources individually for each project. With the new XDC file, the ETL will retrieve resources of all projects areas in one pass. This removes the overhead of the iteration. Rational Insight uses an ODBC driver that has an initialization overhead for every round-trip to the RQM server. For all resources of one project, this overhead sums up to an average from 3 to 5 minutes for each project in a typical server set-up. The new ETL strategy, therefore, minimizes server round-trips and therefore saves this time. For 100 projects, this could save up to 8 hours for every ETL run (delta as well as full loads). The disadvantage of this approach is that in case of an error during the load, you would have to reload much more data than you would for a project by project approach where you would be able to pick up from the project that has failed. In summary, if you manage only a few projects on your RQM server, it is best to stay with the default rqm40.xdc file, even if you have large amounts of data in these few projects. If you have a large number of projects and want to cut out the 3-5 minute overhead per project, then we recommend trying out this new XDC file.

The release also provides a new alternative job for loading RQM's ODS (Operational Data Store) in parallel. It is called RQM_ODS4.0_ParallelDeltaLoad. Depending on your data, this build can significantly improve the performance of loading RQM data in particular during daily delta loads. This new job is used as part of the CLM job stream in Jobs > CLMJobs > CLM4.0_All_Parallel.

New enablement videos

You can find an entire playlist with all new enablement videos for how to create custom reports for RQM and CLM in general at IBM Rational Reporting for Development Intelligence (RRDI).