Rational Quality Manager integration

Rational Quality Manager integration

Overview

Integration with Rational Quality Manager is implemented through the use of an adapter that is installed by default when you install either...

Rational Performance Tester
Rational Service Tester for SOA Quality

The adapter can be run in three modes:

In GUI mode, from within the test workbench itself.
From the command line
As a Windows service

View results

When you run a test script from RQM, the default report displayed during a test run is attached to the RQM results. This report can be customized.
You can view the full run results from within the test workbench by opening the test workbench in the workspace configured to be used by the adapter.

For an RPT schedule with performance requirements, the Performance Requirements report for the last user stage of the schedule will be attached to the RQM results.
For RST for SOA Quality service tests and RPT performance tests, the result completion state reported to RQM reflects the overall verdict of the test log associated to the run.
In many cases a test may contain a failed verification point, but still be considered as passed. You should view the attached report in the RQM execution result and set the execution results status accordingly.
For RPT schedules, the result completion state reported to RQM is based on the overall Performance Requirements status. Only performance requirements for the last user stage defined in the schedule are covered by the report. If no performance requirements are specified, the result completion state in RQM will be set to inconclusive. In this case, you should view the attached performance reports and manually set the completion state in RQM.
If the adapter is running from the command-line or as a Windows service, stop the adapter before opening the test workbench. When the workbench is opened, you can access the full test reporting and test log capabilities. Results for runs initiated from RQM can be found under the RQM Results project.

Troubleshooting

All modes of the adapter use the Eclipse error log. You can view the log by opening the workbench and clicking...
Window | Show View | Error Log

By default, warning and error messages are logged. You can turn on more detailed logging for the adapter by clicking Window > Preferences > Logging. The log component for the adapter is named...
com.ibm.rational.test.lt.rqm.adapter

If you are running the adapter as a Windows service or from the command-line, you can view the adapter.log file without opening the test workbench.

Problem Solution or cause

Where do you look for errors or warnings? In the workbench, click Window > Show View > Error Log.
You do not see the adapter available for selection. Verify that the RQM server address provided to the adapter is correct. Provide the correct address.
Check the login and password provided. Provide the correct password.
Adapter continuously fails to connect to RQM. Verify that the server is running. If necessary, restart the server or check network connectivity.
Adapter shows up red in the selection dialog. The adapter is not communicating with the server.
The adapter may already be in use.
You attempt to import a script from the adapter but no scripts are found.

Make sure the project path entered in the RQM is a project under the workspace associated with the running adapter. You need only to enter the project name. This is less error prone than typing the complete project path, but either forms are acceptable.
If running from the command-line or as a service, be certain the WORKSPACE_DIR set in adapter.config is the same path as seen in the select workspace dialog when running the test workbench. Be careful it's not set to a project folder under the workspace directory.
Verify that you are not using a workspace containing a project that was copied from a shared location. A workspace containing projects from shared locations cannot be used for projects that are not shared.

Adapter is running from the command line or as a service and tests continue to fail. Run the adapter in GUI mode so that you can see what happens when the test workbench runs the test script.
Adapter Windows services does not start. A error message states that the service failed to start in a timely fashion. Verify machine has .NET 2.0 or later.
This platform can be installed from the Windows Update Site or manually.
When testing shared assets, the execution fails with an IOException. Most likely cause is that the RQM to UNC shared location is not setup correctly.

From RQM, ensure that you can access the UNC shared directory without being prompted for a password. You may have to map a drive on Windows for the RQM system to log into the UNC share.
Ensure that you have defined the shared resource in RQM under Admin > System Properties > Resources.
Verify test-script points to a shared location that still exists. If you have associated a RQM test-script with a shared location that has changed (for example if the IP address has been reassigned) you might need to reassociate each test-script
Verify UNC shared directory specified in RQM points to a project.

When testing shared assets, the execution fails with a low level model error. Verify RPT adapter has the required protocol extensions installed. The test assets located on the shared location can only be run on an adapter workspace that supports those protocols.
Service tests created in a previous version of RPT or RST for SOA Quality are unable to execute. Upgrade each SOA asset to the latest version.

Known limitations

When shell sharing RPT and RST for SOA Quality, the adapter registers itself as a RPT adapter.
To register as a RST for SOA Quality adapter, RST must be installed as its own software package.
Running tests from RQM with encrypted data pools is not supported. Password prompting when using such a datapool is not done in the adapter service or in the command-line mode. This is also discouraged in the GUI mode, because it requires user interaction with RPT for a run initiated from the RQM Web user interface.
Only one adapter per product installation on a given computer should be started. Using multiple adapters on the same computer requires that you install each product as its own software package in it's own directory.
For multiple adapters on the same computer, verifyy are using different workspaces.

Related

Rational Quality Manager overview
Configure the RQM adapter
Start and stop the RQM adapter in the workbench
Start and stop the RQM adapter from the command line
Start and stop the RQM adapter as a Windows service
Import test assets into RQM

Problem	Solution or cause
Where do you look for errors or warnings?	In the workbench, click Window > Show View > Error Log.
You do not see the adapter available for selection.	Verify that the RQM server address provided to the adapter is correct. Provide the correct address. Check the login and password provided. Provide the correct password.
Adapter continuously fails to connect to RQM.	Verify that the server is running. If necessary, restart the server or check network connectivity.
Adapter shows up red in the selection dialog.	The adapter is not communicating with the server. The adapter may already be in use.
You attempt to import a script from the adapter but no scripts are found.	Make sure the project path entered in the RQM is a project under the workspace associated with the running adapter. You need only to enter the project name. This is less error prone than typing the complete project path, but either forms are acceptable. If running from the command-line or as a service, be certain the WORKSPACE_DIR set in adapter.config is the same path as seen in the select workspace dialog when running the test workbench. Be careful it's not set to a project folder under the workspace directory. Verify that you are not using a workspace containing a project that was copied from a shared location. A workspace containing projects from shared locations cannot be used for projects that are not shared.
Adapter is running from the command line or as a service and tests continue to fail.	Run the adapter in GUI mode so that you can see what happens when the test workbench runs the test script.
Adapter Windows services does not start. A error message states that the service failed to start in a timely fashion.	Verify machine has .NET 2.0 or later. This platform can be installed from the Windows Update Site or manually.
When testing shared assets, the execution fails with an IOException.	Most likely cause is that the RQM to UNC shared location is not setup correctly. From RQM, ensure that you can access the UNC shared directory without being prompted for a password. You may have to map a drive on Windows for the RQM system to log into the UNC share. Ensure that you have defined the shared resource in RQM under Admin > System Properties > Resources. Verify test-script points to a shared location that still exists. If you have associated a RQM test-script with a shared location that has changed (for example if the IP address has been reassigned) you might need to reassociate each test-script Verify UNC shared directory specified in RQM points to a project.
When testing shared assets, the execution fails with a low level model error.	Verify RPT adapter has the required protocol extensions installed. The test assets located on the shared location can only be run on an adapter workspace that supports those protocols.
Service tests created in a previous version of RPT or RST for SOA Quality are unable to execute.	Upgrade each SOA asset to the latest version.