New & Noteworthy for Rational Quality Manager 6.0.4 M4


Description
Execution enhancements  Roll up test suite and test case results

Roll up test suite results

You can now roll up test suite results, which means that you can compile the results from multiple test suite executions to create a new, consolidated result. The results are rolled up based on the current state of the test suite. In-progress results cannot be rolled up. Results cannot be rolled up if a test suite has more than one instance of the same test case and test script combination.

Example 1: A test suite has five steps. You run the test suite and two steps fail. You then run only the two steps that failed, and they pass. You can use the roll-up operation on the test suite execution record to create a new test suite result that shows all the steps that passed. The new result lists which previous results form the rolled-up result.

Example 2: You run a test suite with a large number of test cases and steps. Something goes wrong after you execute most of the test cases and you cancel the test suite execution. You run the test suite again and ignore the passed steps of the test suite. After the execution is finished, you run a roll-up operation so that the rolled-up result contains all the steps from both the successful executions.

You can use the Browse Test Suite Execution Record (TSER) table and the TSER editor to roll up new test suite results from previous test suite results. You can skip some of the steps from the test suite execution and run those steps later. You can use the Roll Up with Options action to select which test suite results will participate in the test suite roll up. The Related Information panel of the Test Suite Result (TSR) editor shows the test suite results that participated in the roll-up operation. The Browse TSER and TSR tables have a column that indicates whether the result is rolled up.

Image of the TSER table with the Roll Up menu:


Image of the Roll Up with Options dialog box:


Image of the Related Information panel for a rolled up result:



Roll up test case results

In the Test Case Execution Record table and editor you can roll up previous test case results to create a new consolidated test case result. The new rolled-up test case result references the latest step result from the previous test case results for the test data. You can use the Roll Up with Options action to specify which test case results are included in the roll-up. This feature works with manual test scripts. In-progress results cannot be rolled up.

A new execution preference named "Show the previous step results when executing the same test case execution record" is available. If you enable the preference, the last three verdicts are displayed for each step when you execute a manual test script.

Image of previous step results:
Support for PIV smart card and certificate-based authentication


Rational Quality Manager Word/Excel Importer

You can use a PIV smart card or security certificate to authenticate with the Rational Quality Manager server when you start the Rational Quality Manager Word/Excel Importer.

You select an authentication method in the Export to RQM > RM Login Information dialog box:
-User name and password
-SSL certificate
-Smart card 

For more information, see Rational Quality Manager Word/Excel Importer.


Test execution adapters

You can use a PIV smart card to authenticate a Rational Quality Manager server when you start the Rational Quality Manager Command Line or Selenium adapters. To use smart card authentication, you must pass the values for the following arguments when you start the adapter:

-authType - SMARTCARD
-keystoreAlias - Keystore alias (friendly name) for the user certificate

You can also pass the values in the configuration file by using the following property names:

rqm.authType - SMARTCARD
rqm.keystoreAlias - Keystore alias (friendly name) for the user certificate

You can use an SSL certificate to authenticate a Rational Quality Manager server when you start the Rational Quality Manager Command Line or Selenium adapters. To use SSL certificate-based authentication, you must pass the values for the following arguments when you start the adapter:

-authType - SSLCERT
-certificatePath - Path to the SSL certificate. Example - C:\SomeDir\userCert.p12
-certificatePassword - Password for the certificate file. This argument is optional.

You can also pass the values in the configuration file by using the following property names:

rqm.authType - SSLCERT
rqm.certificatePath - Path to the SSL certificate. Example - C:\SomeDir\userCert.p12
rqm.certificatePassword - Password for the certificate file. This argument is optional.

For more information, see the readme files for each adapter.
Table improvements More views of script step information

Columns for script steps
The following columns are now available in the test case execution record (TCER) view:
-Passed script steps
-Failed script steps
-PermFailed script steps
-Inconclusive script steps
-Attempted script steps
-Deferred script steps
-Blocked script steps

These new columns can be filtered and are calculated based on the results of the last execution.


Filters for script steps
The following filters for script steps are now available:

Test Cases view
- Filter by script steps

Test Case results
-Filter by Passed script steps
-Filter by Failed script steps
-Filter by PermFailed script steps
-Filter by Inconclusive script steps
-Filter by Attempted script steps
-Filter by Deferred script steps
-Filter by Blocked script steps

You can use these filters to locate specific artifacts depending the view you are in, or create queries based on any specific number, or range of numbers, for script steps.

Also, all test script step count fields are now available in the Reportable REST API, OSLC REST API, and in PDF and CSV exports.

For details, see Work Item 15905, Work Item 159503, and Work Item 159502.


Execution Status by Number of Steps widget
A new Execution Status by Number of Steps dashboard widget is available that shows the execution status by points for test case execution records, test case results, test suite execution records, and test suite results.

Image of the Execution Status by Number of Steps dashboard widget:


This widget always shows the latest information and does not require a data warehouse. For execution records, the number of steps is calculated based on the last result of the execution record.

The widget shows the following types of reports:
-Table: Number of steps
-Table: Percentage
-Stacked bar chart
-Stacked column chart

Image of the number of steps table:


Image of the percentage table:


Image of the stacked bar chart:


Image of the stacked column chart:


If you click a table cell, stacked bar, or stacked column, the filtered record in the respective table for the test artifact is displayed.
Usability enhancements Edit manual test scripts directly in the keyword editor

The keyword editor has a new section named Edit Test Scripts Inline that enables you to directly edit and save any test scripts that the keyword references. To use this feature, you add the section to any existing keyword. If you create a new keyword by using the Manual script keyword template, the new section is included automatically.

Image of the Edit Test Scripts Inline section:


In addition to editing manual script steps, you can also use this section to edit common properties for the test script, such as the name, description, and categories.
Keywords and parent test scripts can now have different test data

A keyword is associated with a test script, and a test script can be associated with test data. Previously, when keywords were added to a parent test script, the parent test script and the keyword test script had to have the same test data. The association of keywords with test data limited the reuse of keywords.

In version 6.0.4 and later, this limitation does not exist. Keywords and their associated parent test scripts can have different test data. A keyword can be used by any number of test scripts, and all of them can be associated with different test data. When you execute the parent test script, the test data associated with parent test script will be used for the keyword as well as the parent test script. You must ensure that the test data variable in the keyword's test script is also in the parent script's test data.
The Edit Test Scripts Inline section supports comparing configurations

In a configuration-management-enabled project, when you compare any two versions of a test case or a keyword, you can see the differences of the referenced manual test script in the Edit Test Scripts Inline section. You do not have to open the test script editor separately to view the differences between the versions of the referenced test scripts.

Image of comparison support in the Edit Test Scripts Inline section:

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