Rational Quality Manager 6.0.3 New & Noteworthy Details


Description
Administration Provide one test script for each test case

You can associate multiple test scripts with a test case. Now, you can use a new precondition named "Disallow Saving Test Cases without the Required Number of Test Scripts" to restrict the number of test scripts associated with a test case. The new precondition is available under the Save Test Case operation. The precondition displays an error if you attempt to save test cases that do not have the specified number of associated test scripts. To set the maximum number of test scripts, specify a positive integer or leave the value empty for the following options:

• Maximum number of test scripts
• Maximum number of manual test scripts
• Maximum number of automated test scripts

Image of the new precondition:


For more information, see 91103: Provide One Test Script Per Test Case Option.
Artifacts Create artifact references by dragging and dropping

You can now use the browser drag-and-drop gesture to create artifact references. For example, to add test cases to a test plan, you can drag test cases from a browse list in one browser instance and drop them into the Test Cases section in a test plan in another browser instance.

The following browse lists and test artifacts support dragging and dropping to create artifact references:

• From a browse test cases list to a test plan artifact's Test Cases section
• From a browse test suites list to a test plan artifact's Test Suites section
• From a browse test cases list to a test suite artifact's Test Cases section
• From a browse test scripts list to a test case artifact's Test Scripts section
• From a browse test plans list to a test plan artifact's Children Test Plans section

Image of the drag-and-drop functionality:
Improved ability to work with large documents in artifact editors

Previously, the artifact editors had top and bottom action areas where you could access the editor's actions when you scrolled within a document. However, you had to be near the top or the bottom of the document to have the actions in view. Now a static title area is available when you scroll past the editor's actions. You can now access the actions regardless of the document's scroll position.

Image 1: When you scroll in any artifact editor, the title and actions stay at the top:

Image 2: List views have the same behavior
  
Image 3: The test script editor has both the title and actions area and the editor toolbar at the top:
CLM Server Monitoring CLM Server Monitoring removed in 6.0.3

CLM Server Monitoring, a performance monitoring utility included in versions 5.0.2 and later, was removed in 6.0.3. Version 6.0.3 includes a new, lightweight monitoring utility that uses industry-standard MBeans and that can be consumed by other application monitoring services. For more information about server peformance and monitoring, see Plan Item 396673, Work Item 392897, and the Deployment wiki article about Known Expensive Scenarios.
Categories Cross-artifact type categories

A new type of category is available that you can use for all the artifact types in a single configuration. You can modify categories in a single place and see changes reflected for all artifact types.

You can create cross-artifact type categories, or global categories, in the Global Categories section under Artifact Categories. Click the green cross icon to open the creation dialog box, provide a name, and then click Save.

To promote existing categories to global categories, expand the category menu, select the Promote to Global option, and then click Save. The following constraints exist when you promote a category to a global category:

• You can only promote root categories.
• If you promote a category with subcategories, the entire hierarchy is promoted to the global category.

New permissions exist to manage global category actions under the Save Category permissions:

• Global
• Create
• Promote
Set permissions for categories at the team area level

You can now set permissions for categories at the team area level. For example, a category at the project level sets permissions for a single user role, but you can also have a different category at the team area level that sets permissions for that same user role within a team. As part of this change, team area configurations now support Save Category and Save Category Value permissions.
Components Clone artifacts between components

You can now clone artifacts from one component's baseline to your current stream if your stream belongs to a different component. To do this, you must first create a baseline in the component and stream that you want to clone artifacts from. Then, you switch to the component and stream where you want to clone those artifacts to, and select Clone artifacts from another component from the component menu. You then select the baseline and component to clone artifacts from, and select the artifacts you want to refactor. Copies of those artifacts are cloned into your current stream.
Delete and restore components, baselines, and streams

You can now delete components, baselines, and streams on the Manage Components and Configurations page by selecting Delete <item name> on the action menu. You can also restore components, streams, and baselines in the same way that you restore other artifacts: go to Trash View, click View and select Baseline, Stream, or Component accordingly.
New baseline view on the Manage Components and Configurations page

A new Manage Components and Configurations baseline page shows all the baselines that you created for all the configurations in your current active project area. From this page, you can create a new stream from a baseline by selecting Create stream and you can also delete a specific baseline.
PDF reports include component information

Exported PDFs now contain references to components where appropriate.

Table summary PDF reports
When a table view that displays a component column is exported to PDF, the PDF now contains that column as well.

Artifact summary PDF reports
If a component reference appears in the editor for a test artifact, that same component reference appears in the PDF created by exporting the artifact to a summary PDF.
RQM OSLC Configuration Management 1.0 API now supports components

The OSLC Configuration Management 1.0 API now has limited support for the component resource type. The following support is included:

• Reading a feed of component resources
• Reading a component resource
• Component resource shape
• Component selection dialog box
• Component property to rich hovers for all component-aware resources
Plain Old XML (POX) profile requests
• Compliance with the OSLC Configuration Management 1.0 specification

In addition, a component property was added to all component-aware resources resolved by the RQM OSLC Quality Management 2.0 API.

Note: The OSLC Configuration Management 1.0 API component support requires that project areas in Rational Quality Manager are enabled for configuration management. For more information, see OSLC Configuration Management 1.0.
RQM Reportable REST API support for components

The RQM Reportable REST API now has limited support for the component resource type. The following support is available:

• Read a feed of component resources
• Read a component resource
• Create a component resource
• Component property in component-aware resources

For more information, see Rational Quality Manager Reportable REST API.
Switch more easily between components

You can switch easily to another component within or without the current project or global configuration. The Choose a Component dialog box includes the following improvements:

  • Filter the list of components to those components associated with all projects on the server or all projects in the current global configuration.
  • Filter the list of components to those components in the current global configuration.

Image of the Choose a Component dialog box:
Configuration management Compare artifacts of the same type in the same configuration

You can now compare test artifacts of the same type in the same configuration directly from the "Browse <Artifact>" views by selecting two artifacts and using the context menu to select Compare Selected Artifacts > Compare as Source or Compare as Target.

You can compare the following test artifacts in the same configuration:

• Test plans
• Test cases
• Test scripts
• Test suites
• Test case execution records
• Test suite execution records
• Test case results
• Test suite results
Enhanced configuration management permissions

The configuration management process permissions are now more flexible and extensible to support different actions on streams and baselines.
The previous configuration management permissions contained four operations with no actions:

1. Create Stream
2. Create Baseline
3. Modify Configuration
4. Delete Configuration

The current configuration management permissions contain two operations with specific actions:

1. Save Streams
  • Create
  • Delete
  • Modify

2. Save Baselines
  • Create
  • Delete
  • Modify
New RQM Reportable REST API support for configurations

The RQM Reportable REST API now supports the stream and baseline resource types.

Fetching feeds

Fetch the feed of all streams or baselines available on the target server by executing an HTTP GET on the appropriate feed URI.
GET https://localhost:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/stream/
GET https://localhost:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/baseline/

Fetching the details of a configuration

Fetch the details of a particular stream or baseline by executing an HTTP GET on the URI that uniquely identifies that configuration.
GET https://localhost:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/stream/_rbzLQhufEeahafE23YNhDQ
GET https://localhost:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/baseline/_dbzaQhxfEethafEb3YNaDd

Creating a new configuration

Create a new stream or baseline by executing an HTTP POST on the appropriate feed URI.
POST https://localhost:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/stream/
POST https://localhost:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Quality+Manager/baseline/

The response contains the current state of the newly created configuration, including its generated identifier so that you can reference it in other RQM Reportable REST API calls.

For more information, see Rational Quality Manager Reportable REST API.
See the version history for artifacts in configurations

In a project that is enabled for configuration management, it's useful to see an artifact's change history in the context of configurations. For example, you might want to know which configurations the artifact has changes in, which version of the artifact is in the "Release 1 Candidate" baseline, and so on. The version history viewer displays this type of information in a simple graphical view. You can also compare two versions to see their differences.

Image of the version history viewer in QM artifact editors:


Image of the actions available on version nodes:


Image that shows the comparison of two versions:
Support for configurations in the Rational Quality Manager mobile application

The Rational Quality Manager mobile application now supports connections to project areas that are enabled for configurations. To connect to a project area that is enabled for configurations, select the local configuration under the Connection settings menu.
Integrations Rich hover support for test script step results

You can now hover over test script step results in reports created in Report Builder that contain QM Test Script Step Result artifacts, and open the rich hover for the test script step results. When you click the link to the test script step result, you navigate to the test case result that contains the test script step result.

Image of the test script step results rich hover:
Jazz source control Link QM artifacts to Rational Team Concert files

You can now create related resource links between any file stored in Jazz source control and QM test scripts, test case results, and test suite results. Links are established through the Rational Team Concert thick client. For more information, see 398844: Jazz source control: Link SCM-controlled files to other CLM artifacts for traceability.

SCM-linked files in the web client

If an artifact is related to any SCM files, that file link is visible in the new Related Files section in the artifact editor's right sidebar. In addition, a new Linked Files column was added to the Test Script, Test Case Result, and Test Suite Result table views. In this column, you can see the linked files for each artifact resource in those tables.

SCM-linked files in PDF and CSV

When you export the test script, test case result, or test suite result table to a PDF or CSV file, the Linked Files column is included in the resulting document.

SCM-linked files in the Reportable REST API

The Test Script, Test Case Result, and Test Suite Result APIs were updated to include a new "file" element, which represents an SCM-linked file. These elements are included in the resource XML for these elements when the calmlinks=true parameter is used.
Use a Rational Team Concert repository as a shared resource location

In addition to directories on the QM server, you can now use a Rational Team Concert repository as a shared resource location. This feature allows you to store test scripts for adapters in source control.
Manual test scripts Editable custom column for the execution and result views

On the Manual Step Attributes page, you can select a set of custom columns that are editable in the execution and result views. When you run a test script or update a test case result, you can modify values of those custom columns. The value of columns in the parent test script is not affected.

Image of the editable set of custom columns:


Image of the modified values:
Execute manual test script steps in any order

You can execute the steps of a manual test script in any order apart from the current sequential order. To enable this option, set the required administrator preference on the Manage Project Properties > Execution Preferences page.
Filter manual steps by custom columns

You can filter the manual steps table in a similar way to other table views. You can enter filter arguments and click the Run icon to filter the manual steps. The filter control is available for all the custom columns of the script. The step filtering is available in the Stack Left to Right view of manual test scripts.

Image of the filter control:
New Information step type for manual test scripts

You can create an Information type step when you author a manual test script by using the row-level menu or a keyboard shortcut (Ctrl + D + Enter). An Information step is a non-executable, read-only step while execution occurs. To enable an Information step type for manual test scripts, set the required administrator preference on the Manage Project Properties > Test Script Preferences page.
Resize manual steps table beyond the page width

You can resize the columns of a manual steps table beyond the page width. The table columns are resized to their actual width and no other column width is affected. A horizontal scroll bar is shown if the table width exceeds the page width. To use this feature, you can open the Change Column Display Settings dialog box and select the Actual width: Columns can expand beyond the page width option.

Image of a table sized beyond the page width:
Project areas New process template for Scaled Agile Framework (SAFe) 4.0

A new Quality Management process template is provided for Scaled Agile Framework (SAFe) 4.0. This process template provides preconfigured elements that are commonly used in Scaled Agile Framework (SAFe) projects, including a single timeline with a Value Stream iteration that contains two Programs with iterations aligned to the Change Management timeline for the SAFe Portfolio. Also included are SAFe-specific artifact templates and categories, and a preconfigured project dashboard template. Use this template to create a SAFe-enabled full testing portfolio that supports SAFe 4.0.
Reporting Include Quality Management components in Report Builder reports

In Report Builder, when you use a Lifecycle Query Engine (LQE) data source, the component artifact is available in the Change and Configuration Management category for reporting on Quality Management components.
Table views Create a test suite or test plan when you view test cases in the table view

Two new table actions were added to the Test Cases table view. When you select Associate Test Cases with New Test Plan, a new test plan is created with the information that you specify, and the selected test cases in the table view are associated with the new test plan. When you select Associate Test Cases with New Test Suite in the Test Cases table view, a new test suite is created with the information that you specify, and the selected test cases in the table view are associated with the new test suite. When you select Associate Test Cases with New Test Suite in the Test Cases table view of the test plan editor, a new test suite is created with the information that you specify, the selected test cases in the table view are associated with the new test suite, and the new test suite is associated with the test plan in the editor.
Double-click to manipulate columns in the Change Column Display Settings window

In the Change Column Display Settings window, which you can open in any table view, you can now double-click in the column entries to add an entry from the Available Columns list to the Display Columns list and remove an entry from the Display Columns list to return it to the Available Columns list.
Enhanced UI for setting and running default queries in table views

The default query capability of any table view is now enhanced. The Run Default Query button now includes a tooltip that shows the default query. The Set Default Query button now contains a drop-down menu to directly update the default query for the artifact type of the displayed table view. You can select from the following menu options:

• Use the current selected saved query of the table view as default
• Reset to not use any default query
• Select a saved query from a chooser dialog as default
• Use the default query set for the project area

To maximize the available space of the page for any table view, the filter sidebar honors the setting of "Show the filter sidebar when a table view is opened" of the Table View Settings user preference. When this setting is cleared (default), the filter sidebar remains closed when the default query or any saved query is run. Note: The filter sidebar is not closed if you explicitly open it.
Group by test suite in the Execution Console window

A new column named Test Suite was added to Execution Console window. This new column supports group by, filter, and sort actions. The column is not displayed by default; you add it in the Change Column Display Settings dialog box.

Image of the Test Suite column:


For more information, see 146798: Provide the ability to "Group By" Test Suite in the Execution Console.
Test automation traceability Associate a test script with a test suite:

The test case section of the test suite has a new Run a test script option. You can select that option and click the plus sign (+) to associate an automation script with the test suite.

Image of the Run a test script option:


Consider an implementation for the Selenium adapter. In the image, a Selenium script named Selenium is associated with the test suite. The Selenium test script has three JUnit functions:

   • testGoogleWDJUnit4
   • testWikipediaWBJUnit4
   • testWikipediaWBJUnit4_test2

Three test cases were created with names to match the Selenium JUnit functions: testGoogleWDJUnit4, testWikipediaWBJUnit4 and testWikipediaWBJUnit4_test2. No test script is associated with those test cases. Instead, the test script is associated with the test suite. The three test cases are also added to the test suite.
Improved support for test automation traceability

Previously in Rational Quality Manager, one automation test script tested only one test case. However, in production scenarios, a single automation might actually test multiple test cases. That single automation script runs once and creates a result for all the test cases that are tested by that test script. In this release, you can run an automation script and create results for all the test cases that are tested by that automation test case. This functionality is achieved by allowing the test suite to have a single automation script. This new capability was added for test suites. Test suites also have the list of test cases that are tested by the automation script. If you run the test suite, the automation script runs and creates results for the test cases associated with the test suite as well as for the suite.

For more information, see 150783: [QM] Improved test automation traceability support.
New test suite project preference

You can enable or disable the new Use test script in test suite capability in the preferences for test cases and test suites under Manage Project Properties.

Image of the new capability:
Run a test suite in test script mode

When you run the test suite, which has the Run a test script option enabled, the automation script, which is associated with the test suite, is run, and not the test cases associated with the test suite.

Image of the Run Test Suite dialog box for the test script mode:


In this mode, you can perform the following actions from the Run Test Suite dialog box:
   • Schedule execution
   • Create a result without executing
   • Modify execution variable values

Click Finish to go to the automation script execution page; not to the suite execution console. After the execution is complete, click Show Result to go to the test suite page.

The result for the three test cases associated with the test suite are displayed in the Result Details section of the test suite result.

Image of the script execution page:


Image of the test suite result:
Sample Selenium adapter

In the Selenium adapter implementation, any adapter that supports this new feature must have a new capability named MULTIPLERESULTS. The adapter task has a special flag to specify that it is a test script execution from test suite isSingleScriptSuiteExecution. If this flag is set to true in the adapter task XML, it signals a special type of script execution for the adapter to perform. The adapter task also contains the URI of the test suite result. If you run a GET command on it, you get the suite element. The suite element contains the newly added test case name, newly added test case URI, and the test case execution record URI that is required to create test case results. After the automation tool completes the execution, the adapter performs the following actions:

   • The adapter reads the automation log and creates the results for all the suite elements. In the current Selenium adapter, the test case name in the suite element is matched with the JUnit test function name in the Selenium script. The adapter POST command creates one result for each suite element.
   • The adapter updates the suite element with the result URI and removes the status of the test suite result (which is in progress) and PUTs the test suite result.
   • The adapter updates the task to mark it complete. No test case result is associated with the adapter task.
Test execution Run automated tests in parallel across multiple computers

Currently, if the execution preferences option of "Select a single machine for the test suite if all steps in the test suite contain the same type of test script" is enabled, test cases in a test suite are assigned to a single computer only. A new execution preference named "Select from all available machines in a test cell if the test suite is configured to run in parallel mode" is located under the preference "Select a single machine for the test suite if all steps in the test suite contain the same type of test script." This option enables you to distribute test cases in a test suite among all available computers if the test suite is run in parallel mode within a test cell.

Image of the new execution preference:


For more information, see 145794: Provide the ability to run automated tests in parallel across multiple machines when the execution preferences option of  "select a single machine for the test suite if all steps in the test suite contain the same type of test script" is enabled.
Test results Compare test results in the same configuration directly from the editor

You can compare two test results in the same configuration directly from the test result editor by clicking the new Compare with a different test case result action in the upper right and by selecting a different test result from the list. A compare screen opens so that you can see the differences and perform any merges, if necessary.

This action is enabled for the test case result and test suite result editors.

© Copyright IBM Corporation 2016  |  Contact  |  Privacy Policy  |  Terms of Use