QADirector - Release Notes - 6.1

QADirector components can be installed on one machine or on separate machines. Users must have administrator permissions to install QADirector. The minimum system requirements for each component are as follows:

QADirector integrates with many automated testing, analysis, defect tracking, and requirements management tools by default. If you intend to use QADirector with any of these tools, please note the minimum version requirements:

Micro Focus Products

• Quality Manager 6.0, 6.0.1

• Optimal Trace 5.2, 5.3

• QALoad 5.8, 5.9

• QARun 4.9.1 SP 2

• TestPartner 6.0, 6.1, 6.2 (build 449), 6.3

• TrackRecord 6.3 build 289 or later. Not supported on Vista or Windows 7.

Third-Party Products

• Atlassian JIRA 3.12.3, 3.13

• Borland CaliberRM 2006, 2008

• Bugzilla 3.2.4, 3.4

• Compuware Delivery Manager 1.1

• Compuware File-AID/CS (ComparePro, ConverterPro) 4.1, 4.2

• Compuware Hiperstation 7.7, 7.8

• Microsoft Visual Studio Team Explorer 2005, 2008

This section describes the new features available in this release.

Micro Focus Acquires Compuware Quality Solutions Products

On June 1, 2009, Micro Focus purchased Quality Solutions products from Compuware Corporation. Newbury, England-based Micro Focus provides enterprise application management and modernization solutions. Compuware and Micro Focus will continue to collaborate to ensure that customers receive uninterrupted service and obtain the full value of both companies' product capabilities.

For the most recent product updates and information, go to SupportLine, the Micro Focus customer care Web site. You can find the new contact information posted on SupportLine in an updated Release Notes for each product and in future product release documentation.

Reports

Script Results Report

Lists all scripts and steps for all jobs in the selected result folder.

Test Execution Status by Priority (Execution) Report- Requirements Folder

Displays the number of tests with each result status based on the risk level by selected requirement folder, execution cycle, and planning cycle.

Test Execution Status by Priority (Execution) Report - Tests Folder

Displays the number of tests with each result status based on the risk level by selected test folder, execution cycle, and planning cycle.

Test Execution Status by Requirement (Planning) Report

Displays the number of tests with each result status for each requirement in the selected requirement folder and with the selected planning cycle.

Change History

Change history includes several usability enhancements designed to make it easier to find and report on the changes you are looking for:

• Tracking changes for requirement folders and test folders is now available.

• You can print or export a report on all changes to an asset.

• The Change History dialog box now includes a filter that allows you to select the asset type and action.

Defects Center

The Defects Center includes several usability enhancements to simplify creating and editing defects: you can now open a defect by double-clicking it and you can create a defect with the Submit Defect button.

Additionally, new fields have been added for when you submit a defect from QADirector to your defect tracking tool: Project name, Script comment, Risk, Requirement folder, and Result folder.

Integrations and Platform Currency

Microsoft TFS Integration

QADirector now contains a direct integration with the Microsoft Team Foundation Server defect tracking system.

Platform Currency

QADirector now supports Windows 7 and Oracle 11g.

Note: For Windows 7, you must install and configure the QADirector application server using the built-in Administrator Account.

Hiperstation/MVS Batch

Hiperstation/MVS Batch integration is available in this release via RUMBA.

This section describes known issues related to the current release.

QADirector Integration Plug-In Installation

Installation in environments that contain Microsoft SQL Server, or other Microsoft development tools that enable support for JIT Debugging, may cause the JIT debugging window to be displayed showing an unhandled error in the MSI. This is a known conflict and does not keep the installation from completing successfully.

Upgrading from 5.3.1

After upgrading from 5.3.1, the system configuration database connection information will be lost. You need to re-enter the information after upgrading. On the QADirector web server, click Start>All Programs>Micro Focus>QADirector>System Configuration.

Configuration File Changes

• After migrating QADirector, the values in TmApp.config are reset to the default values.

• For Quality Manager integration, if the logging level is not set to ALL in the TmApp.config for the Subscriber and Scheduler, the integration with Quality Manager will not allow projects and clients to push.

Hiperstation and MVS Batch integrations

When executing a Hiperstation or MVS Batch test, if there is a copy of RUMBA running, it must be closed before submitting the test for execution.

Change History

After migration, change history tracking options for several asset types are reset to track Delete only. Administrators should verify proper asset configuration in the Change History tab of Administration>Application Configuration.

Test Management Server

After installation, the Test Management Server must be manually restarted before Test Execution Agents are recognized.

Oracle

Patch

In early versions of Oracle 9i that have long text exceeding 1,000 characters, the text gets truncated. To resolve this issue, upgrade to the latest patch for 9i, which is 9.2.0.8. Oracle 10g does not have this issue.

Post-Migration

After migrating, the QM/DM Configuration Web server name field may become blank in the Administration - Application Configuration dialog box. Open the dialog box, re-enter the information, and then click OK.

Cycles

Cycle Filters Post-Migration

After migrating from 6.0, filters that were based on Cycles need to be reset to accommodate the new implementation of Cycles. Open the filter and select the appropriate row and then select the correct cycle from the Value list.

Reports

Custom Attributes and Filters

Default custom attributes are not displaying in reports when using a filter. Updates to the custom attributes must be made to the default custom attribute before they display in the reports.

Filter Criteria

When displaying the filter criteria in reports, choose to display on top of the report. Displaying the filter criteria on the bottom of the report distorts some graphs.

Launching QADirector Reports from Quality Manager

When QADirector reports are being called in the Quality Manager project context and the QADirector database is configured to an Oracle migrated database, the login is treated as if NTLM is checked in QADirector. It tries to login as the first user in the Users table of the database. If that user has clients associated with it, it will log in as that user. If no clients are assigned to that user, a dialog displays giving the appropriate message. Selecting Yes on this dialog box resumes normal login. No does nothing.

Using QALoad with QADirector

If a session id has a transaction set to 0, the QALoad Conductor opens but the session id is not executed.

Window Not in Focus

A known issue exists with the Microsoft Windows operating system that may cause new programs to appear behind other already open programs. When you start a program from another program, the new program window may appear behind all other open windows. Additionally, the new-window icon flashes on the taskbar. This symptom occurs on a Microsoft Windows 2000-based computer or on a Microsoft Windows XP-based computer. Microsoft has documented a procedure that details how users can modify the value of the ForegroundLockTimeout registry entry in Registry Editor to correct the issue. For specific instructions and more information on this issue, please refer to the following article located at the Microsoft Help and Support website for details: http://support.microsoft.com/default.aspx?scid=kb;en-us;886217

Installing QADirector on the same Server as SharePoint Services 3.0

QADirector cannot share the same web server as SharePoint Services 3.0 on Windows Server 2003.

Submitting the First Defect from QADirector to a Clean TrackRecord Database

Submitting a defect from QADirector for the first time to a clean TrackRecord database may result in the defect not appearing to exist. It is recommended to have at least one defect pre-existing in the TrackRecord database prior to submitting defects from QADirector.

Running the Scheduler on Windows 2003 Server

On 64-bit Microsoft Windows 2003 Server, the Scheduler (running in 32-bit mode) may stop. This is related to a known issue with .NET. If you experience this, you can install the following patch from Microsoft to correct the issue.

KB913384: http://support.microsoft.com/kb/913384

Removing QADirector

There is a known issue with the InstallShield Wizard when uninstalling products on certain environments. If you uninstall all of the components of QADirector and then reboot the computer, you may receive a File Not Found error message. Click OK to dismiss the message.

This section includes technical information that may affect how you use QADirector.

Embedded Execution Plans

Regarding the Tech Alert that indicated that the advanced feature of embedded execution plans (execution plans within other execution plans) be avoided: That issue has been resolved in this release.

Web Server Configuration

All users should log out of the application before making any changes to the web server configuration, for example rebooting or changing servers.

License File Placement

Place QADirector license files in a directory accessible to all users on a machine. Do not place license files on the Microsoft Windows Desktop or in the My Documents folder. These locations are accessible only by the user logged in at that time. For more information regarding license management, refer to the Distributed License Management License Installation Guide.

Node Locked License

Node locked licenses are not allowed or provided in this release. A license server must be installed. For additional information, refer to the documentation for Distributed License Management 4.2.

Migrating Suites

For 5.3.1, all suites are migrated to execution plans and placed in the All Test Center Folders in the Execution Center. Any migrated suites/execution plans that were created from the Requirements Center no longer contain links to requirements. You can create new execution plans from the Requirements Center using the Quality Optimizer. The new execution plans are linked to requirements and placed in the Default Requirements Folder in the Execution Center.

Isolating Databases before Upgrading

You may want to review the changes in the newest version before installing on your production server. The best way to do this is to create a test environment. To ensure the integrity of your production database, you should isolate it. The most secure way to isolate a test database from your production database is to install the two databases on separate database servers. This prevents accidental upgrading of your production database. If you prefer to create a test environment before upgrading to the latest version of QADirector, isolate your existing database as follows:

Note: Do not use different versions of QADirector on the same database. The following procedure isolates a database on the database server, but does not prevent users from establishing a new connection to the database. If this happens, the database will automatically update, possibly causing data loss.

1. Back up the existing QADirector database. Store the backup in a safe place.

2. Create a new QADirector database instance.

3. Restore the existing QADirector database to the new database instance.

Running Compuware File-AID/CS ComparePro Scripts

When integrating with QADirector, Compuware File-AID/CSComparePro sets do not execute. If you are using ComparePro sets, this issue has been fixed in SP5 for File-AID/CS 4.1. The service pack is available on the Compuware support website.

Running QALoad Scripts

When integrating with QALoad 5.7, QADirector completes the test job before the QALoad Conductor has executed the load test. A service pack is available to address this issue through Customer Support.

QADirector Integration with TrackRecord

TrackRecord uses FairCom® Server to store all persistent data and runs it as a Windows service "TRDBService" on the TrackRecord database server machine. With all TrackRecord integrations, it is important to allow enough time to stop and start the TRDBService properly. If this service has not finished starting, the TrackRecord database is not available. If this service stops abnormally, the TrackRecord database can be corrupted. For additional information, refer to SupportLine.

If ever you have any problems or you would like additional technical information or advice, there are several sources. In some countries, product support from Micro Focus may be available only to customers who have maintenance agreements.

If you obtained this product directly from Micro Focus, contact us as described below. If you obtained it from another source, such as an authorized distributor, contact them for help first. If they are unable to help, contact us as described below.

However you contact us, please try to include the information below, if you have it. The more information you can give, the better Product Support can help you. But if you don't know all the answers, or you think some are irrelevant to your problem, please give whatever information you have.

• The name, release (version), and build number of the product.

• Installation information, including installed options, whether the product uses local or network databases, whether it is installed in the default directories, whether it is a standalone or network installation, and whether it is a client or server installation.

• Environment information, such as the operating system and release on which the product is installed, memory, hardware/network specifications, and the names and releases of other applications that were running.

• The location of the problem in the product software, and the actions taken before the problem occurred.

• The exact product error message, if any.

• The exact application, licensing, or operating system error messages, if any.

• Your Micro Focus client, office, or site number, if available.

Contact

Our web site gives up-to-date details of contact numbers and addresses. To connect, enter www.microfocus.com in your browser to go to the Micro Focus home page, or go to http://supportline.microfocus.com.