New & Noteworthy for Rational Quality Manager 6.0.6


Description
Build artifacts Hover preview windows for build records and build definitions

When you hover over a build record or build definition, a window is displayed that contains information about the build artifact.

If a build record contains available build verification test (BVT) information, click Show More to see the BVT information and build definitions that are associated with the record.

Image of the hover preview window for a build record:
Compare and merge Differences are highlighted in the Summary section

When you compare two artifacts or two versions of the same artifact, differences between values in the Summary section are now highlighted. The values include the artifact's built-in attributes, category values, and custom attributes. In the Summary section, use the Accept action to accept the values from the source artifact.

Image of two test cases compared in the Summary section:
Configuration management Warning messages for requirements links in local configurations

When you work in a project that is enabled for configuration management, you should use a global configuration, which contains the configurations of contributed streams from various applications. If Rational Quality Manager is in a local configuration, there is no way to resolve requirements links from Rational DOORS Next Generation without knowing the configuration of the Rational DOORS Next Generation stream.

If you are working in a local configuration, a warning message is displayed to use a global configuration. The warning is displayed in the hover content of requirements links in the editor sections and the related information sections. An application-level warning is also displayed at the top of the page.
Custom attributes Rational Quality Manager Reportable REST API supports CRUD and query requests for custom attributes

The Rational Quality Manager Reportable REST API now supports creating, reading, updating, and deleting (CRUD) and querying a custom attribute type:

https://<server>:<port>/<context>/service/com.ibm.rqm.integration.service.IIntegrationService/resources/<project area>/customAttribute

For more information, see New resources in Rational Quality Manager Reportable REST API.

The query support includes fields selection and filtering:

https://<server>:<port>/<context>/service/com.ibm.rqm.integration.service.IIntegrationService/resources/<project area>/customAttribute?fields=feed/entry/content/customAttribute[title='custom attribute title 1']

For more information, see fields in Rational Quality Manager Reportable REST API.
Excel importer Configuration file syntax for user-defined priority values

You can define the priority values of a test artifact by using string literals. These values do not convey the literal meaning of priority. For example, to define a test suite's priority as high, you use this configuration file syntax: testsuite.priority="literal.priority.130".

Previously, if you had user-defined priority values, you had to manually edit large sets of Excel data to map those values. Now, a new configuration file syntax is available that enables you to define priority values by using the optional #define syntax.

Examples:
  • #define LITERAL.PRIORITY.130 {high, top, 3} // high priority
  • #define LITERAL.PRIORITY.120 {,,} // medium priority
  • #define LITERAL.PRIORITY.110 {} // low priority
  • #define LITERAL.PRIORITY.101 {undefined} // undefined priority
User-defined priorities do not support user-defined priority values.

Note: Undefined priority values are not translated and are not sent to the server. If a priority value matches a custom priority, the server processes it. Otherwise, the server assigns default values for the priority.

For more information, see Rational Quality Manager Word/Excel Importer: Priority value mapping.
Jazz source control Link Rational Quality Manager artifacts to Rational Team Concert files

You can now create related resource links of the type "References" from any file stored in Jazz source control to Rational Quality Manager test cases. Links are established through the Rational Team Concert Eclipse client.

SCM-linked files in the web client
If a test case is related to any source-control-managed (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 is available in the test case 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 a test case 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 case 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.
Linking Visual indicators for link direction and storage

When you create a link between artifacts in different applications that have project areas enabled for configuration management, the link is stored in one of the applications. A requirements link in Rational Quality Manager is stored in Rational Quality Manager, and not in Rational DOORS Next Generation, while a quality task link in Rational Quality Manager is stored in Rational Team Concert.

To clarify which application stores a link, direction indicators are now displayed in these locations to indicate whether the link is incoming or outgoing:
  • Editor sections
  • Related information sections
  • List view column headers
  • Link action labels
Image of direction indicators for related information sections:
Manual test scripts Merge steps modified during execution by using the test script editor

During manual execution, users with the appropriate permissions can add, edit, and delete steps by using the row-level actions for each step. After the execution is complete, users can merge the changes back into the test script by using the Compare with Test Case Result Steps button in the Manual Steps section of the test script editor. Use this button to select the modified test case result and merge its modified steps back into the test script.

The browse test script table has a new column named Step Merge Status that you can use to filter test scripts. By default, the step merge status of all test scripts is empty. If steps are modified, added, or deleted during execution, the step merge status changes to Pending. When you merge changes back into the test script, the step merge status changes to empty. You can also perform the Compare with Test Care Result Steps action from the browse test script table.

Keep test script steps without merging by using the browse test case result table
In the browse test case result table, use the Compare with Test Script Steps > Keep Test Script Steps action to keep the current test script without merging with the modified result steps. This action marks the step modification status of the selected test case result as Merged.
Remove requirement or defect links by using The Remove hover action button

In the test script editor, you can remove the requirement link associated with a manual test script step by using the Remove action button that appears when you hover over the link. Similarly, in the test case execution and test case result editors, you can remove the defect link associated with a manual test script step by using the Remove action button that appears when you hover over the link.
OSLC integrations Link test cases to architecture elements of an OSLC AM provider

You can link Rational Quality Manager test cases with architecture elements of an OSLC architecture management (AM) provider such as Rhapsody Model Manager. To create these links, you must add an association between the Rational Quality Manager project area and the AM project area.

Architecture Elements menu
The Rational Quality Manager action bar menu now includes an Architecture Elements menu, which is hidden by default. To display the menu, change the setting in the project area editor, under Menu Organization > Main Menu. You can use the Architecture Elements menu to create or view architecture elements.

Architecture Element Links section
The test case editor now includes an Architecture Element Links section. You can add the section to a test case by using the Manage Sections dialog box. The Architecture Element Links section shows the architecture elements that are linked to the current test case. You can use this section to add, create, and remove architecture element links.

Validates Architecture Elements column
The test case table view now includes a Validates Architecture Elements column. You can add this column by using the Change Column Display Settings dialog box. The Validates Architecture Elements column shows the architecture elements that are linked to test cases. You can add and remove architecture elements by using the inline cell editing menu.
Process templates Importing queries with missing references

Shared saved queries are now integrated with process templates, which means that you can create new project areas based on a process template that contains saved queries. The saved queries might contain filters that reference artifacts that apply only to the project area in which they were created. By default, those types of saved queries are not created in the new project area.

To change this behavior and create all saved queries, even if they reference artifacts that do not exist in the new project area, you can change an advanced property on the Server administration page. By default, the following property is set to true:

com.ibm.rqm.planning.service.internal.QueryFilterMigrationTask

Delete imported queries with missing references: Queries that are imported from a process template might reference artifacts that do not exist in the new project area. Enable this option to delete these queries.
New SAFe 4.5 process templates

The following SAFe 4.5 process templates were added for creating a project area:
  • Quality Management for Essential SAFe 4.5
  • Quality Management for Full SAFe 4.5
  • Quality Management for Large Solution SAFe 4.5
  • Quality Management for Portfolio SAFe 4.5
Reporting

Jazz Reporting Service reports include more artifact information

 

Previously, Jazz Reporting Service reports that used Lifecycle Query Engine as a data source did not include some information for artifacts. Now, the reports include the following artifact information:

 

Test scripts

  • Total test script steps

Test cases

  • Total test script steps

Test case execution records

  • Is blocked

Execution results

  • Attempted script steps

  • Blocked script steps

  • Deferred script steps

  • Failed script steps

  • Inconclusive script steps

  • Passed script steps

  • Permanently failed script steps

  • Skipped script steps

  • Total script steps

  • Host name

  • Roll up

  • Total points

  • Custom properties

Suite execution results

  • Attempted script steps

  • Blocked script steps

  • Deferred script steps

  • Failed script steps

  • Inconclusive script steps

  • Passed script steps

  • Permanently failed script steps

  • Skipped script steps

  • Total script steps

  • Roll up

  • Is current

  • Test cell

Reviews Prevent specific users from reviewing or approving test artifacts

A new precondition named Disallow Specific Users as Reviewers and Approvers was added for the Save Formal Review operation. This precondition prevents the following users from reviewing or approving a test artifact:
  • Owner of the test artifact
  • Originator of the test artifact
You can select one or both preconditions.

Image of the new precondition:
Test cases Precondition and post-condition sections in the Test Case Result editor

New precondition and post-condition sections were added to the Test Case Result editor. These sections display the content from precondition and post-condition sections of the associated test case at the time of execution.
Run Test Case dialog box can be resized

You can now resize the Run Test Case dialog box horizontally. The resized width is saved and used the next time that you reopen the dialog box.
Test Items section in the Test Case Result editor

A new Test Items section was added to the Test Case Result editor. This section lists the work items that are related to test case results that do not affect or block the result, such as work items that are not defects.
The Normative and Informative Documents section is now displayed in exported PDF files

When you add the Normative and Informative Documents section to a test case, that section is now displayed in the PDF file when you choose one of the following export options:
  • Summary Export
  • Details Export
  • Comprehensive Export
Test environments Send an ID for the test environment to RQM adapters

When a test case runs, the data that is passed to the adapter (the execution request) includes the test environment name, not the identifier of the test environment or the URI for the test environment. Because duplicate names are allowed for test environments, the adapter cannot determine which test environment to use.

Now, a unique identifier is passed with the test environment name so the adapter can determine which test environment to use. This unique ID field is visible in the Execution Variables section of a test case result.

Image of the test environment ID with the test environment name in the Execution Variables section:
Test execution

Automatically delete artifacts when a test case or test suite is no longer referenced from a test plan

You can now automatically delete test case execution records (TCERs), test suite execution records (TSERs), and their previous execution results when the execution record references a plan and a test case or test suite, but the plan no longer references the test case or suite.

TCERs and TSERs are deleted as part of a scheduled background task which occurs once a day by default. To modify the schedule frequency, go to Advanced Properties and change the "Case and Suite Unreferenced by Plan Clean Up Task Fixed Delay" setting.

Automatically update the Time Spent field in test case execution records

Previously, you had to manually update the Time Spent field of a test case execution record after it ran. Now, a new preference named Calculate time spent of a test case execution record once its execution is over was added under Manage Project Properties > Execution Record Preferences. If you enable this preference, the Time Spent field of the test case execution record is automatically updated after it completes the current execution by subtracting the end time from the start time of the last result.

Image of the new project property:
Distribute the weight of a test case result based on the actual result of the test case result

By default, the weight distribution of a test case result depends on the verdict of its step results. Consider an example where the weight of a test case result is 100 and it has four step results. Three step results are passed, one step result fails, and the overall actual result of the test case result fails. The passed point of the test case result is 75 and failed point is 25.

A new project property named Calculate weight of a test case result based on actual result was added under Test Result Preferences. If you enable this preference, the weight distribution of the test case result is based on the actual result and not on  the verdict of the step result. Because the actual result failed in the example, the failed point of the test case result is 100 and the passed point is 0.

Image of the new project property:
Execution tool has new -testCellName and -testCellItemId arguments

The execution tool has two new arguments: -testCellName and -testCellItemId. When you run a test case execution record (TCER) or test suite execution record (TSER), you can provide the test cell by using either of these arguments.

-testCellItemId=<testCellItemId>: Item ID of the test cell from which adapters are selected during the execution of a TCER or TSER.
-testCellName=<testCellName>: Name of the test cell from which adapters are selected during the execution of a TCER or TSER. This argument is ignored if the -testCellItemId argument is provided.
Identify a TCER or TSER to run based on additional input variables

If an ID is not provided for a test case execution record (TCER) or test suite execution record (TSER) to run, the execution tool now supports these additional input variables to locate a TCER or TSER:
  • Test suite or test case ID: -testCaseId=32 (-testSuiteId=123) Note: The testSuiteId or testCaseId argument is required if the TSER or TCER ID is not specified.
  • Test plan ID: -testPlanId=21 (To search an execution record within a test plan).
  • Test environment: -testEnvironment=Android (To search an execution record that runs on a specified test environment).
  • Current iteration: -currentIteration=true  (To limit the search to the current iteration only).
  • Last created execution record: -runLastCreatedER=true (To select the most recently created execution record if multiple execution records are associated with a test case or suite).
You can provide at least one -testCaseId or -testSuiteId argument and as many as all five arguments to identify a TCER or TSER to run.

Note: These additional arguments are required only when a TCER or TSER ID is not specified.
Move a defect at the step level during manual test execution

When you run a manual test, you can add a defect at the step level. During test execution, you can now delete a defect from the current or a previously executed step and add it to another executed step.
New Current for Build column in the Test Case Results and Test Suite Result List views

Previously, a gap existed for reporting on test case results or test suite results based on builds. This gap surfaced when you reran test case execution records (TCERs) against a specific build, and then ran the same TCERs against a different build.

Example of the previous behavior:
  • You have 10 TCERs. You run the 10 TCERs against build A.
  • 3 of the 10 TCERs fail, so you run them against build A again. After this run, you have 13 test case results and 10 of the results are marked as Current.
  • The next day, you run the same 10 TCERs against build B. You cannot report on the current results for build A, because the new results from build B are marked as Current.

To address this issue, a new Current for Build column was added. Previously, the current results were available for only a TCER. Now, you can apply a Current for Build flag to show the current results for a TCER and build record combination. For each TCER and build record combination, only one test case result can have the Current for Build flag set to true. Similarly, for each test suite execution record (TSER) and build record combination, only one test suite result can have the Current for Build flag set to true. The Current for Build column is available in both the Browse Test Case Result and Test Suite Result List views. The column supports filtering, sorting, and grouping.

Now, to report on a specific build, you can create a shared query where Build=<build record name> and Current for Build = true. You can use this query in dashboard widgets such as Test Statistics, Test Matrix, and so on.

The Current for Build flag for existing test case and test suite results will be updated by the asynchronous migration task. To check the status of the "Current for build flag on Test Case Results Migrator" and "Current for build flag on Test Suite Results Migrator" tasks, go to https://<server>:<port>/qm/migration.
New column filters in the Add Step dialog box for execution schedules

You can add a test case execution record and a test suite execution record to an execution schedule by using the Add Step operation. Column filters are now available for all columns in the Add Step dialog box for both test case execution records and test suite execution records.

Image of the Add Step dialog box with column filters:
Preconditions and post-conditions are displayed by default in the test case execution console

Previously, during test case execution, the precondition and post-condition sections of a test case were collapsed by default and only displayed the title and section description. Now, the two sections are expanded by default and their contents are displayed. The section description is in context-sensitive help, which is displayed when you hover over the help icon.
Prevent test environments from being edited if execution records were previously run

New project properties were added under Execution Record Preferences to prevent test environments from being edited if test case execution records and test suite execution records were previously run. The new preferences are Do not allow changes to the test environment if a test case execution record was previously run and Do not allow changes to the test environment if a test suite execution record was previously run.

Image of the new project properties:
Rerun a test suite result

You can now rerun a test suite result from the test suite result editor and the Browse Test Suite Result view. The following attributes are automatically picked up from the previous run:
  • Test suite steps: Even if the test suite is updated with a new or modified step, the rerun operation takes the suite steps from the previous test suite result, not from the test suite.
  • Test suite execution record
  • Execution variable value that was set in the previous run at the test suite level
  • Execution mode
  • Whether execution variables are passed between scripts
  • Whether to stop suite execution if test cases do not pass

When you rerun a test suite result, you select the following options in the Rerun Test Suite dialog box:
  • The build record
  • The test cell or single adapter to run all tests if steps contain same type of automated test script
  • Whether to exclude passed steps from execution

Image of the Rerun Test Suite dialog box:
Run actions are available in each row in a TCER list view

Previously, to run a test case execution record (TCER) from the list view, you clicked the row actions menu icon; then, from the drop-down menu, you clicked Run Test. Then, from another drop-down menu, you clicked Run to start the execution. The same multiple clicks were also required to resume a paused execution.

This release includes a simpler way to start the execution. When you hover over an entry in the TCER list view, if the Last Result column is displayed (default), the Run icon is displayed beside the last result icon. This icon provides a simpler one-click option. If the execution is paused for the TCER, the Resume icon is displayed.

The TCER list view also appears in the Test Artifact dashboard viewlet, and this capability is available in that viewlet.
Run multiple test case execution records from a table view

You can now select and run multiple test case execution records from a table view. When you run multiple test case execution records, a dialog box opens where you select test cell, build record, and schedule execution options, and see the number of tests selected for execution. When you click Finish, the selected records are placed in an execution queue and you can access them in the execution console. You can select and run multiple test case execution records for all types of tests such as manual tests, automated tests, or tests without scripts.

Image of the Run Test Cases dialog box:

Show the test start time for both test case and test suite execution

The status of the adapter task is shown as in progress when the adapter takes the task for execution. Previously, the time was not shown when the adapter picked the task. Now, the test start time is displayed both on the execution page as well as in the execution console.

Image of the test start time on the execution page:


The start time for test suite execution is the earliest start time of its associated test cases. When a test suite runs in sequential mode, the start time of the test suite is the start time of the first test case of the test suite. When a test suite runs in parallel mode, test cases can run in any order based on the availability of the adapter. The start time of the test case that starts running first is the start time of the test suite execution. The start time of the test suite execution is displayed in the suite execution console, which also displays the test start time of each test case.

Image of the test start time in the suite execution console:

The Run Test Case dialog box shows test case execution records in a table view

In the Run Test Case dialog box, existing test case execution records are now shown in a table view on the Use an Existing Test Case Execution Record tab. You can sort or filter the table to select which test case execution records to run. You can create a new test case execution record by using the Generate a New Test Case Execution Record tab.

Image of  the Run Test Case dialog box:
Test scripts Change the step type for multiple manual test script steps

You can now change the step type for multiple manual test script steps at the same time in a bulk operation. Select one or more steps and open the step-level menu to change the step type of the selected steps. If the selected steps include a step of type Keyword or Execution Variable, the step-level menu will not have the actions to change the step type. You can change the selected steps to these types:
  • Execution Step
  • Reporting Step
  • Information Step
Upgrading OSLC asynchronous migration

OSLC asynchronous migration is a background process that runs after an upgraded Quality Management (QM) server is started. The migration manages migrators, which run a set of tasks on specific artifact types that require migration and publishes patch events in the Tracked Resource Set 2 (TRS2) feed that contains the changes. The execution is asynchronous and does not prevent the server from working or users from performing normal activities while the migration is running. Some features might not be displayed in Jazz Reporting Service until the migration is finished.

OSLC  migration status console
Administrators can use the asynchronous migration console to monitor and prevent a migrator from running. The console is available at the following location:
https://<domain>:<port>/<qm-context>/oslcMigrationStatus

In the table, each row represents a project area. The status and total number of migrated items are displayed for each project area.

Project area: Displays the project area name
Status: Displays the current migration status for this project area
Items migrated: Total number of migrated items

Migration status
Not started: Migration has not started for this project area
In progress: Migration is currently running for this project area
Complete: Migration is completed for this project area
Usability enhancements Copy the link for the current page as rich text

In 6.0.5, the Copy link for this page action was introduced to copy the URL of the current page. This action was enhanced to copy the link as rich text for browsers that support it such as Google Chrome and Microsoft Internet Explorer. If you paste the copied rich text link in applications that support rich text, such as Microsoft Outlook and IBM Notes, the title of the page is displayed as a link, with the URL set as the HREF attribute of the link.
Description column in the browse test case table

An optional Description column was added to the browse test case table. To add this column, use the "Change column display settings" dialog box. The new column is also available during a CSV or PDF export of the browse test case table.
Easily insert images into the rich-text editor

Drag and drop images
To insert images in the rich-text editor, you can now drag and drop images from the local file system into the editor. The supported image file formats are BMP, GIF, JPEG, and PNG. The supported browsers are Mozilla Firefox, Microsoft Internet Explorer, Google Chrome, and Safari.

Paste images from the clipboard
To insert images into the rich-text editor, you can copy a full image or part of an image onto the clipboard and then paste it into the editor. The supported browsers are Mozilla Firefox and Google Chrome.
Filter icon in the Test Artifact dashboard viewlet

A Filter icon was added to the header of the Test Artifact dashboard viewlet. The filter provides the same text search capability as the text search in Rational Quality Manager artifact list views.
Improved navigation to the Filter By panel

In artifact list views, a button is now available to open and close the left navigation pane. The navigation pane is organized into tabs, which makes selecting the Filter By panel easier.

Image of the artifact list view with the navigation pane closed:


Image of the artifact list view with the navigation pane open:
Updated navigation and organization in the Project Properties window

In the Project Properties window, the groupings of project properties are now organized and displayed as tabs. When you select a tab, the group's properties are displayed on the left, which streamlines the display and makes navigating to the group's properties easier.

Image of the Project Properties window:

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