Rational QualityArchitect
Release Notes
Release 2001.03.00
Part Number: 800-023988-000
Copyright © 2000 Rational Software and its subsidiaries. All rights reserved.
November 2000Scope - Product Definition
Guidelines and Restrictions on Using Rational QualityArchitect
- Using Fully Qualified Class Names
- COM
- Logging Failures with COM Stubs
- Lookup Tables
- Limitations with COM Programmatic ID Strings
- Session Recorder
- Launching the Session Recorder from the Toolbar
- Connecting to Remote Application Servers
- Online Help
- Windows Help
- Missing Java Classes for Query Builder and Session Recorder Help
- Verification Points in Scenario Testing
- EJB Query Builder
- Using the OLE DB Query Design Wizard and the IBM DB2 ODBC Driver
- Using the IBM JDBC Driver
- Order of Jar Files on the Classpath
- Visual Cafe
- Stack Overflows
- Running the Sample Application in Visual Cafe
Contacting Rational Technical Support
Scope - Product Definition
This release of Rational® QualityArchitect is designed specifically for testing the following component types:
Rational QualityArchitect is a powerful collection of integrated tools for testing middleware components built with technologies such as Enterprise JavaBeans and COM.
QualityArchitect, in conjunction with Rational Rose, generates test scripts for components and interactions in your Rose model. Once generated, the test scripts can be edited and run right from your development environment or from Rational TestManager.
Guidelines and Restrictions on Using Rational QualityArchitect
Using Fully Qualified Class Names
When using QualityArchitect to generate tests or stubs, make sure that fully qualified class names are used for parameter types and return types. For example, use java.math.BigDecimal and NOT just BigDecimal. Failure to use fully qualified class names will result in code that will not compile without adding additional import statements.
COM
Logging Failures with COM Stubs
When COM stub code is compiled as a part of an activeX.exe, multiple debug executions of the script from the Visual Basic IDE cause logging from stubs to fail.
Stubs will still be functional, however. Each logging call in the stub will wait for a timeout causing script execution to be slow.
To avoid this problem, shutdown Visual Basic after each debug execution of the script.
Lookup Tables
Lookup tables cannot be opened for editing after execution of a COM VB unit test that calls a stub. This only occurs if you execute the script from within VB. When you do so, the following error appears:
"The data file for [lookup table name] could not be opened".Limitations with COM Programmatic ID Strings
COM Programmatic ID strings must be 39 characters or less. Since there is no check on this limitation in RQA, a .cls name combined with the VB Project name may exceed 39 characters. VB will not allow you to run if you do not trim down the length of the Programmatic ID string.
The error will appear as follows:
"ProgrammaticID string too long '<VB project name>.<RQA cls
The Programmatic ID must be 39 characters or less"
Session Recorder
Launching the Session Recorder from the Toolbar
In order for the EJB Session Recorder to run successfully, the home interface classes and remote interface classes for the deployed EJBs must be referenced in the user CLASSPATH. These classes can be referenced in a directory or in a jar file.
Also, the required application server classes must be referenced in the user CLASSPATH. Consult you application server documentation for information about the required application server classes.
To start the Session Recorder from the toolbar:
Connecting to Remote Application Servers
When trying to connect to a remote application server, the required jndi initial context classes for the application server must exist in the local CLASSPATH. If the application server classes are not found, the EJB Session Recorder will not be able to connect to the remote server.
Online Help
Help for QualityArchitect is provided in the form of standard Windows Help files, JavaHelp, and HTML. In addition, an electronic version of the printed manual is available on the Rational Solutions online documentation CD.
Online Help for the QualityArchitect toolbar and for dialog boxes that are launched from Rose are standard Windows Help files. This help contains links to the online manual, which is HTML-based.
Online Help for the Session Recorder and for the Query Builder is JavaHelp-based.
Windows Help
Online Help for the QualityArchitect toolbar and for dialog boxes that are launched from Rose are provided as standard Windows Help files. You can display online Help for Rational QualityArchitect by clicking in the RQA toolbar and pressing F1 or by clicking the Help button in many of the dialog boxes. Note that it can take several seconds for the Help to first appear.You can display online Help for Rational QualityArchitect by clicking in the RQA toolbar and pressing F1 or by clicking the Help button in many of the dialog boxes. Note that it can take several seconds for the Help to first appear.
All of the procedures in the online Help are actually links to topics in the HTML-based online manual. These links sometimes fail because of the way that this Help file was invoked. If the link fails:
- Ctaddin.hlp is the online Help for Rational QualityArchitect. This file should reside in the top-level directory where you installed Rational QualityArchitect.
- Double-click to open ctaddin.hlp.
- Navigate to the topic that contained the link.
- Retry the link that had failed.
Missing Java Classes for Query Builder and Session Recorder Help
The JavaHelp v.1.1 that is integrated with the Query Builder and the EJB Session Recorder requires JDK v.1.1.8 or above to fully utilize all the help features. Because Visual Age for Java (VAJ) v.3.1 only utilizes JDK 1.1.7., some of the required classes for JavaHelp are missing. As a result, when the JavaHelp jar file is imported into VAJ v.3.1, some problems are generated that state certain Java classes are missing. These missing classes include the following:
- java.awt.print.PageFormat
- java.awt.print.Printable
- java.awt.print.PrinterJob
- java.security.PrivelegedExceptionAction
- java.security.Permission
- javax.swing.JLabel$AccessibleJLabel
Verification Points in Scenario Testing
If you generate a scenario test and you want to insert a verification point (VP) when prompted, and you select DatabaseVP from the Verification Point Type dialog, RQA launches a Query Builder dialog to help you define a VP. In this dialog, you enter JDBC connection information to a SQL database.
In order to use the JDBC driver, you must add the JDBC driver's .jar or .zip file to the system CLASSPATH. The Query Builder will append the System Classpath to its own internal classpath.
EJB Query Builder
EJB Test scripts that contain static database verification points, and thus use the Query Builder wizard, require the JavaHelp JAR file (jh.jar). This JAR file must be included in the IDE's classpath. Otherwise, a
NoClassDefFoundErrorwill be generated when the Test Script is executed. Specifically, this happens if you add a static VP with the OPTION_USER_ACKNOWLEDGE_BASELINE option set in the test script or you have incomplete VP information.Using the OLE DB Query Design Wizard and the IBM DB2 ODBC Driver
Because of compatibility problems with the OLE DB Query Design Wizard and the IBM DB2 ODBC Driver, you will need to enter SQL statements manually when using this combination.
The following error appears when you attempt to use the Query Design wizard:
[IBM][CLI Driver]SQL0104N An unexpected token "END-OF-STATEMENT" was found following "<TABLE OWNER>.<YOUR TABLE NAME>". Expected tokens may include "JOIN <joined_table". SQLSTATE=426 Please contact IBM Technical Support for DB2 ODBC Driver resolution."Using the IBM JDBC Driver
If you connect to DB2 via IBM 's JDBC Driver, you need to be aware of:
- The character set or code page used by the DB2 database
- The character set used by client applications
The character code page on the client and the target DB2 server must be compatible, that is, the DB2 server must minimally be able to convert the client code page into the DB2's internal code page. If this fails, the DB2 server will throw an "incompatible code page error message."
Example: If you attempt to configure a DB2 ODBC data source to be used by IBM's COM.ibm.db2.jdbc.app.DB2Driver on a Korean NT4.0 machine with the target server being on a US English DB2 server, you'll get an error message relating to incompatible code page.
In this case, you must consult the IBM documentation or IBM Tech Support on resolving this issue.
Order of Jar Files on the Classpath
If a J2EE JDK is installed on a pre-J2EE application server, the pre-J2EE jar files must precede the J2EE jar files on the class path. For example, weblogicaux.jar should precede the standard JDK 1.2.x jar files if the WebLogic version is pre-J2EE (i.e 4.5x).
For information about connecting to application servers, consult the vender's documentation.
Visual Cafe
Stack Overflows
If a stack overflow occurs in Visual Cafe when you attempt to build a project that contains generated test scripts:
Running the Sample Application in Visual Cafe
To run the Rational Bank Account sample EJB application in Visual Café:
- Launch Visual Café 3.1 if it is not currently running.
- Create a new Empty Project:
- Click Project > Options and then click the Directories tab.
- Click New, the button farthest to the left.
- Click file.
- Navigate to Rational Test\QualityArchitect\Samples\ejb/bankacct\vc\RatlBankAcct.jar and click Open.
- Click the Project tab.
- In the Main Class box, type RationalBankAcct.BankAcctClient.
- In the Program Arguments box, enter the following text:
appserver=weblogic- Click OK.
- Click Project > Execute.
Contacting Rational Technical Support
If you have questions about installing, using, or maintaining this product, contact Rational Technical Support as follows:
Note: When you contact Rational Technical Support, please be prepared to supply the following information:
| Rational Software Corporation http://www.rational.com support@rational.com |