| Description | |
|---|---|
| Administration |
Prevent state transitions for artifacts that have pending approvals A new precondition called Pending Approvals is available. This precondition prevents an artifact from transitioning to a different state when any review or approval is pending for the artifact. This precondition enables team members to be added as a reviewer or approver for artifacts that they are concerned with, and the artifact cannot change states until they complete their review, or are removed from the review. The following artifacts support this new constraint:
|
| Authentication |
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:
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. |
| Build records |
Append the build web ID to the build record name For builds that are generated automatically from Rational Team Concert to Rational Quality Manager, you can now automatically append the web ID to the build name in this format: <Name> (ID:<webID>) |
|
Create build records and build definitions through a command-line script at run time You can now create a build record by using a command-line script and associate the build record with the result that is created by executing the script. Sample command in a Windows environment: echo RQM_BUILDRECORD_NAME=Rec >> "%qm_ExecutionVariablesFile%" If a build record named "Rec" does not exist in the project area, it is created and associated with the test case result that is created by executing the command-line script. If a build record named "Rec" already exists, the existing build record is associated with the test case result that is created by executing the command-line script. If more than one build record named "Rec" exists, the value for the execution variable RQM_BUILDRECORD_WEBID is used to find the correct build record. You can also create the build definition from the command-line script and optionally associate it with a build record. Sample command in Windows environment: echo RQM_BUILDDEFINITION_NAME=Def >> "%qm_ExecutionVariablesFile%" If build definition named "Def" does not exist in the project area, it is created. If a build definition named "Def" already exists, a new one is not created. If more than one build definition named "Def" exists, the value for the execution variable RQM_BUILDDEFINITION_WEBID is used to find the correct build definition. echo RQM_BUILDRECORD_NAME=Rec >> "%qm_ExecutionVariablesFile%" echo RQM_BUILDDEFINITION_NAME=Def >> "%qm_ExecutionVariablesFile%" When both the build definition and build record are specified in the command-line script, the build record is associated with the build definition. |
|
|
Enforce unique names for build records You can now set a project property so that each build record in a project area has a unique name. This option helps prevent the same build record from being created multiple times and helps avoid confusion between build records with the same name. |
|
| Categories |
Enhanced hierarchy view for the category administration editor The category administration editor now contains an enhanced hierarchy view (formerly known as the outline view) with enhanced capabilities. In this view, the category structure is displayed as a tree, so that you can see the dependency between categories and subcategories, and create or manage the category hierarchy. When you select a category in the tree, a panel on the right lists all the values that are associated with the category. You can use the paged display in the panel to see, create, associate, edit, and remove category values. |
|
Improved experience for working with large category value sets When you work with very large category value sets in Rational Quality Manager, such as thousands or more, the overall experience and load time is now improved for artifact editors and browse lists. When you view, select, or choose category values, the values are displayed in a searchable, paged list. You can search and browse categories in this list, which you open by using the More option when category values are displayed. For example, category values are displayed when you perform these actions:
|
|
|
Improved navigation for selecting categories You can now navigate through and locate category values more easily by paging through them or searching on text. The new paging support is available in the summary section for all artifacts that support categories. When you first click the selector, an initial set of values is displayed. Image of an initial set of values:  If the number of available values is greater than 15, a More option is displayed. When you click More, a dialog box opens that contains page navigation links and a text search filter. Image of the dialog box with paging and search: 
|
|
| Compare and merge |
Minor updates to the artifact compare and merge views 1. Sections that do not show differences, such as the Formal Reviews, Summary, E-Signature, and other sections, are now noted. Image of a view that does not show differences:  2. For sections that show differences, it is now clearly noted when no differences exist. Image of a section with no differences:  3. Differences for test script steps and test suite steps are now annotated in target-only and source-only terms and styles, which is consistent with other annotations. 4. Comparisons for test suite steps used to show a No Differences message, even when there were changes. Changes are now correctly noted. Image of correctly noted changes: 
|
|
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: 
|
|
| Configuration management |
Drag and drop Rational Quality Manager configurations In Global Configuration Management, you can now drag streams and baselines from the Rational Quality Manager configuration picker into a valid location in a global configuration. |
|
New "Enable only baselines" mode supports creating multiple baselines, but not components or streams A new mode for configuration management is available that enables you to create multiple baselines, but that does not add the complexity of multiple streams and components. You can enable this mode in a project area that does not support configuration management, but not in a project area that already supports configuration management. Image of the Enable only baselines option:  If you enable this mode, you can later enable the full configuration management capabilities, but you cannot disable the support for baselines within the project area. Specific baseline permissions are available that you can use to control access and updates. In this mode, there is no integration with the Global Configuration Management application. Integrations with other applications, such as Requirements Management and Change and Configuration Management applications, behave the same way as when configuration management is not enabled. There is no support for reporting against baselines. In a project area that is enabled for baselines, you cannot create new snapshots of test artifacts. You can still see any existing snapshots. Baselines enable you to see the state of your project area at a given point in time. You can switch your view to a baseline, but you cannot change any items within a baseline. If you permanently delete an item in the Trash view, that item is deleted from the baseline (as it is for snapshots). You can use the version tree to compare the current version of an artifact with its version in a baseline, and you can see a full comparison of all artifacts that are different from a baseline. |
|
|
New option to scrub components You can now scrub a component to remove all information about it. For example, you might scrub a component if it contains sensitive information that should not be exposed, such as after a data spill. The new Delete and Scrub the Component menu option is available on the Manage Components and Configurations page in the Components panel. Only users who have the permissions to both delete and scrub components see the menu option. When you select this option, all instances of the name, description, and history of the component are removed. The component is then renamed and archived, and you can restore it if you need it again. The component's configurations are also archived. |
|
| Lab management |
New calendar for reserving lab resources A new calendar with Day, Week, and Month views is available for viewing and managing reservations for lab resources. You can adjust the calendar attributes, such as size, time, and duration, to suit your needs. The calendar also provides color codes for different types of reservations, such as reservations for the current user and other users, or for modified or conflicted reservations. Image of the new calendar:  The calendar contains capabilities for moving, resizing, or deleting reservation periods, and supports reservations that repeat on a daily, weekly, monthly, and yearly basis. When reservations repeat, you can modify the date, type, and number of repetitions. You can change a single reservation to repeat, or change a repeating reservation to a single instance. If you cancel any repeating instance of a reservation, all instances are canceled. Image of the new calendar with reservations that repeat: 
|
| Linking |
Add all test cases with linked requirements in the Reconcile window In the Reconcile window, you can now add all test cases that are associated with requirements to the test plan by clicking Select All. The test cases with linked requirements are added to the test plan even if requirements that do not contain test cases are selected. |
|
Automatically link test cases in a test suite to the test plan that contains the suite A test suite contains a list of test cases. Similarly, a test plan contains a list of test cases and test suites. Previously, when you added a test suite to a test plan, Rational Quality Manager did not automatically add the test cases associated with the test suite to the same test plan. Now, project preferences are added to address this scenario. Image of the project preferences to synchronize test cases and test suites in test plans:  When you select the When a test suite is added to the test plan, automatically add the associated test cases of the test suite to the test plan option, all test cases that are associated with the test suite are added to the test plan when you add a test suite to the test plan. You do not need to add the test cases separately. When you select the When a test case is added to the test suite, automatically add the test case to all editable parent test plans of the test suite option, the other option (When a test suite is added to the test plan, automatically add the associated test cases of the test suite to the test plan) is also selected automatically. If you select this option, when you add a test case to a test suite, the same test case is automatically added to all the parent test plans of the test suite, except for locked and approved test plans. |
|
| Manual test script steps |
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. |
|
Edit manual test scripts directly in the test case editor The test case editor has a new section named Edit Test Scripts Inline that enables you to directly edit and save any test scripts that the test case references. To use this feature, you add the section to any existing test case. If you create new a test case by using the Basic manual test case 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. |
|
|
Remove and correct HTML tags in manual script steps that are migrated from Rational TestManager If you migrate scripts from Rational TestManager to Rational Quality Manager, you might see malformed HTML tags in manual script steps. For example you might see malformed tags such as <br/gt; or double-encoded tags such as <br/> (where the & character is missing before the g). These characters represent the HTML tag <br/> or a carriage return. If this malformed code is saved at some point during the migration, the intended carriage returns are not shown and the HTML characters are displayed, which can make step descriptions difficult to read. A REST API utility command was created to correct these characters and to show the script step text with the intended carriage returns. For details, see Work Item 47236: Remove and correct HTML tags shown in Script Steps after TM Migration. |
|
| Table views |
Filter columns in list views by excluding results In list views, you can now filter the column contents by excluding results. For example, if you want to see all the test case execution records that do not belong to certain iterations, you can exclude those iterations from the Iterations column. Image of the Exclude option for the Iteration column:  As another example, to see a list of test case execution records whose last results were not generated for a specific build, you can filter the results by using the Doesn't contain option. Image of the Doesn't contain option for the Build for Last Result column: 
|
|
Resize columns in artifact table views beyond the page width You can now resize the columns in artifact table views beyond the page width. The table columns are resized to the actual width that you specify and no other column widths are affected. A horizontal scroll bar is displayed if the table width exceeds the page width. To use this feature, open the Change Column Display Settings dialog box and select the Actual width: Columns can expand beyond the page width option. You can apply this preference to all table views by using the My Preference for Quality Management > List View Settings dialog box. |
|
|
Set a default display for columns in the Test Case section of a test plan If you have the Administrator role and change the column display settings of the Test Cases section of a test plan, you can now save those settings as the project-wide default for tests plans. If you select this option, all test plans in the project have those column display settings for the Test Cases section, unless someone explicitly changes them. Users can override the default settings by setting their own preferences, and you can also change the settings for individual test plans. |
|
|
Set default column display settings for list view sections in editors If you have the Administrator role and change the column display settings for a list view section of an artifact editor, you can now save those settings as the project-wide default of the section and also as the artifact-specific default for some of the sections. If you select the option to save the settings as artifact-specific, that takes precedence over the project-wide default of the section. Each artifact can have its own column display settings. You can update or remove the artifact-specific default settings through the "Change column display settings" dialog box. Each user can override the default settings by setting a personal preference. The personal setting is saved automatically each time the user changes the column display settings. Personal settings are applied to the editor section, not the individual artifact. If the section has both default settings (project-wide or artifact-specific) and personal settings, there is an option to switch between the two settings in the list view of the section. By default, all sections use the personal settings when the list view is opened. A user preference is available to override the personal settings and use the default settings instead. These editor sections support project-wide section defaults and artifact-specific defaults: Test Plan Editor
These editor sections support project-wide section defaults only, and no artifact-specific defaults: Test Case Result Editor
|
|
|
Set the table cell display style for all list views You can now set the table cell display style for all list views by using "My Preferences for Quality Management." In the Preferences window, on the List View Settings page, there is now a section where you can set the table cell display styles, such as word wrapping and font size, for all list views. Image of the new preferences for List View Settings:  These settings are applied to all list views, including selection lists in dialog boxes. However, you can still retain or change the table cell display settings for individual list views. To change the settings for an individual list view, in that view, click the Change Column Display Settings action and set the preferences for the view. Image of the settings for an individual list view: 
|
|
|
Update a custom attribute for multiple artifacts at the same time In tables that show custom attributes, you can now update a custom attribute for multiple artifacts at the same time. When you select artifacts in the table, you can assign a single value for a custom attribute for all the selected artifacts. This update option for custom attributes is supported for the following artifact type tables and sections:
|
|
|
Use the date format from the client browser when exporting to CSV When you export content from a table view to a CSV file, you can specify to use the date format from the client browser instead of the international standard date format. You set this new option in Advanced Properties under the "com.ibm.rqm.print.service.PrintService" category and the "Use the date format from the client browser when exporting to CSV" property. |
|
| Test cases |
Associate test cases in the list view with an existing test plan or test suite In 6.0.3, a capability was introduced so that you can create a test suite or test plan when you view test cases in the list view. Now, you can associate test cases that are selected in the list view with an existing test plan or test suite. When you associate test cases with a test plan or test suite, you can either create a new test plan or test suite (default action) or select an existing one. For the test cases in the Test Cases section of a test plan, similar to creating a new test suite from selected test cases, the existing test suite that you select is added to the test plan if it is not already included. |
|
Duplicate test cases in a test plan The Duplicate Test Cases action was added to the Test Cases section of the test plan editor. This action is similar to the one on the Test Cases list view page, but without the option to choose a project area. When you perform this action, the selected test cases are duplicated in the same project area and are added to the test plan. |
|
| Test execution schedules |
New Executable ID column in the Steps table for execution schedules A new Executable ID column is available in the Steps table in the execution schedule editor. The column lists the ID of the added test suite execution record (TSER), test case execution record (TCER), or automation. Image of the Executable ID column: 
|
|
New Schedule Now capability for execution schedules A new Schedule Now capability is available in both the execution schedule editor and the execution schedule list view. With this capability, you can trigger the execution schedule after 1 minute. For example, if you want to trigger the execution schedule with different trigger conditions, such as the date and time or build completion status, you can use the Schedule Now option to schedule it for the next minute without affecting the trigger condition. Also, row-level actions were added in the execution schedule list view. Image of the execution schedule editor with the Schedule Now button:  Image of the execution schedule list view: 
|
|
|
New columns in the Add Step dialog box for adding TSERs to execution schedules When you add a test suite execution record (TSER) as a step to an execution schedule, new columns are available in the TSER list so that you can more easily find TSERs. The following columns were added to the Add Step dialog box: 1. Test Suite 2. Environment 3. Test Plan 4. Iteration Image of new columns in the Add Step dialog box: 
|
|
| Test execution |
New keyboard shortcut for running tests You can now open the Run dialog box by using the keyboard shortcut Ctrl+Shift+X. This new shortcut applies to test cases, test suites, test case execution records, and test suite execution records. |
|
New rich-text support for updating the execution status of the command-line adapter You can now use rich text to update the execution status of the command-line execution script. The qm_ExecutionPropertiesFile (execution.properties) file now includes an additional richtext property that accepts HTML content up to 100 characters. The HTML content that you enter is displayed as the execution status of the command-line script. Image of a sample command-line script:  Image of the execution page: 
|
|
|
Pauses during manual test execution are now recorded and used to calculate the actual run time When you pause a manual test and then resume it later, the duration of the pause is now recorded and used to calculate the actual run time of the manual test. Both the paused time and actual run time are reported in the test case result. Image of the Paused Time and Actual Run Time fields:  The test suite execution also records the time paused between the execution of suite steps. The test suite result also reports the paused time and the actual run time. |
|
|
Set one test suite step adapter ID for all test suite steps in the Rational Quality Manager Command Line Execution Tool In the Rational Quality Manager Command Line Execution Tool, you can use the new "adapterIdForAllSuiteStep" argument to specify a single adapter for all the steps of the test suite. |
|
|
When command-line or Selenium test scripts start running, associated TCERs are set to In Progress When you run a manual test script, the status of the associated test case execution record (TCER) is set to In Progress and an In Progress test case result is also created. In previous releases, this behavior did not occur for remote test script execution. Instead, a test case result was created only after the execution of the remote script was complete. Now, the behavior for command-line and Selenium adapters has changed. When you run a command-line or Selenium test script, an In Progress result is created when the adapter starts executing the test script and the status of the TCER is also changed into In Progress. |
|
| Test results |
Delete test results from the Previous Results Details section of TCER and TSER editors You can now delete test case and test suite results directly from the Previous Result Details section of test case execution record (TCER) and test suite execution record (TSER) editors. |
|
Open the execution result page by pressing Enter After script execution is complete, you can open the associated execution result page by pressing Enter on the script execution page. |
|
|
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:  Rolled-up result verdicts A rolled-up result contains verdicts from the most recent result. If the verdict is missing or deferred for some steps, the previous result is used as the verdict for that step. A new execution preference is available to mark the test case result as Deferred if you cancel or stop the execution. Permissions to roll up results You must enable permissions to be able to roll up results. The permission to roll up test case results is available at this location: Project area editor > Permissions > Save Test Case Result > Create Roll Up Result The permission to roll up test suite results is available at this location: Project area editor > Permissions > Save Test Suite Result > Create Roll Up Result Admin preferences By default, the rolled-up result is set as current execution result for test cases and test suites. You can disable this behavior by resetting the "Set the rolled-up result as the current execution result for test cases and test suites" preference on the Manage Project Properties > Execution Preferences page. When test case execution is canceled or stopped, currently all unexecuted steps are marked as Inconclusive. To mark all unexecuted steps as Deferred, set the "When test case executions are canceled or stopped, set unexecuted steps as Deferred" preference on the Manage Project Properties > Execution Preferences page. Last Rolled-Up Result column for execution records table view You can add a Last Rolled-Up Result column to the Test Case Execution Records and Test Suite Execution Records table view by using the Change Column Display Settings dialog box. The Last Rolled-Up Result column shows the status of the last rolled-up result. |
|
| Test scripts |
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. |
|
New option to automatically synchronize the state and lock status between test scripts and test cases In the test case editor, in the Edit Test Scripts Inline section, an option is now available to automatically keep the test script's state and lock status synchronized with the test case. If this option is enabled, when you change the test case's state or lock status, the test script's state or lock status is also updated. Image of the new option in the Edit Test Scripts Inline section:  The option to synchronize the state and lock status of the test script with the state of the test case is not applicable to a user-defined workflow. |
|
| Usability enhancements |
Copy and Replace function now includes options for copying links The Copy and Replace function now provides the same copying options for links as the Duplicate function. The default copying option is the same as the original Copy and Replace behavior. Image of Copy and Replace options for copying links:  Additionally, the Copy and Replace function no longer requires multiple parents of the artifact to perform the function. |
|
Icons for artifact types now have labels The editors in Rational Quality Manager display icons to differentiate artifact types. For new users, the artifact types might not be apparent from the icon. To improve usability, the label of the artifact type is now included below the icon. |
|
|
Make bulk edits to custom attributes You can now make bulk edits to custom attributes in several artifact views. When you perform a bulk edit, you can select multiple artifacts in a table and then assign a single value for a custom attribute of the same type to those selected artifacts. You can make bulk edits to custom attributes in the following artifact type tables and sections:
|
|
|
PDF reports now contain the same artifact icons as the web client In the web client, artifact names are typically accompanied by an icon that identifies the type of artifact, such as a test case, test script, test suite, and so on. PDF reports also contain the icons to identify artifacts, including these newly added icons:
|