Component test tools - release notes


1.0 Known problems
   1.1 Execution of a second EJB component test suite with stubs fails on WAS 5
   1.2 Cannot test EJBs using both local and remote interfaces in the same test project.
   1.3 Problem starting WebServices component tests generated from WSDL files
   1.4 CTA Web Service: Web Service URL displayed in the Test Suite editor could be wrong for some WSDL
   1.5 CTA WebService : Changing the server for a WS stub could imply changing it on some other stubs
   1.6 Testing EJB, default deployment data are often wrong
   1.7 Session Facade Pattern: Call to same EJBs Methods are skipped
   1.8 Making a cell empty in the data table
   1.9 A remote interface and a locale interface cannot be tested in the same test project
   1.10 I18N: Documentation: Limitation in viewing exported CTA Result on Mozilla
   1.11 [Data Tables] Contextual menu on the header column not accessible
   1.12 *testcodelib.jar path is absolute
   1.13 Two successive EJB component test executions of different test suites with stubs are impossible on WAS 5
   1.14 I18N: component test project name shoud not use DBCS
   1.15 EJB Deployment: no explicit error message if server name missing in deployment tab for WAS5.x
   1.16 Duplicate attributes for GregorianCalendar 'set properties' value class
   1.17 *Viewing response time or hit rate reports for a URL Test

1.0 Known problems

1.1 Execution of a second EJB component test suite with stubs fails on WAS 5

When running an EJB component test on WAS 5.0 or 5.1, previously run tests might cause this new test execution to fail. Try stopping and restarting the application server.

1.2 Cannot test EJBs using both local and remote interfaces in the same test project.

When two tests are defined in the same test project, and one is testing an EJB using the local interface, and the other one uses the remote interface, the test project will not compile and therefore cannot be executed.

1.3 Problem starting WebServices component tests generated from WSDL files

It is not possible to start Web Service component tests that are generated from WSDL files containing identifiers with non-ASCII characters.

1.4 CTA Web Service: Web Service URL displayed in the Test Suite editor could be wrong for some WSDL

Execution of a second EJB component test suite with stubs fails on WAS 5. When running an EJB component test on WAS 5.0 or 5.1, previously run tests might cause this new test execution to fail. Try stopping and restarting the application server.

1.5 CTA WebService : Changing the server for a WS stub could imply changing it on some other stubs

Changing the server for a Web Service component stub might impact other stubs. If several Web Service component stubs have been defined from the same WSDL file, and the WSDL file contains more than one service, or more than one port in a service, changing the server of one of those stubs will in fact change the server for all the stubs.

1.6 Testing EJB, default deployment data are often wrong

If many application servers are configured in the workspace, the default deployment settings used when creating a new EJB component test will use the first application server configuration found, and not the one that is specific to the EJB under test. Users have to edit the test suite and modify the deployment settings.

1.7 Session Facade Pattern: Call to same EJBs Methods are skipped

The session facade test pattern only takes into account the first call to an EJB when creating the test behavior, instead of taking into account all calls. If necessary, users can add the missing calls manually in the automatically generated test behavior.

1.8 Making a cell empty in the data table

Using the Ctrl+X shortcut on a cell of the Test Data Table will not completely clear the cell content. To clear the cell content completely, right-click on that cell and select the "clear" option.

1.9 A remote interface and a locale interface cannot be tested in the same test project

It is not possible to test EJBs using both local and remote interfaces in the same test project. Create one test project to test an EJB's local interface and another test project to test the EJB's remote interface.

1.10 I18N: Documentation: Limitation in viewing exported CTA Result on Mozilla

The Mozilla browser does not properly display exported component test execution results that have been generated with a Run configuration that is named with a double-byte character set.

1.11 [Data Tables] Contextual menu on the header column not accessible

The only way to access the context menu on the header columns of test data tables is by right-clicking with the mouse. Doing so enables you to add, remove, or rename data sets.

1.12 *testcodelib.jar path is absolute

If you export a test project and then use it in a different location, you might need to update the path to the testcodelib.jar library.

Note: This has been fixed in V6.0.0.1.

1.13 Two successive EJB component test executions of different test suites with stubs are impossible on WAS 5

When running an EJB component test on WAS 5.0 or 5.1, previously run tests might cause this new test execution to fail. Try stopping and restarting the application server.

1.14 I18N: component test project name shoud not use DBCS

Double-byte character sets (DBCS) are not supported for the component test project name.

1.15 EJB Deployment: no explicit error message if server name missing in deployment tab for WAS5.x

When you configure an EJB component test to run on WAS 5.1, the "server instance name " field in the deployment tab of the Test Suite editor is left empty. This will prevent the test from running. Exceptions are displayed in the WAS 5.1 console. To correct the problem, enter the correct server name manually.

1.16 Duplicate attributes for GregorianCalendar 'set properties' value class

In the test data table, when using the set properties option for the GregorianCalendar class, the last two attributes ('FirstDayOfWeek' and 'MinimalDaysInFirstWeek') are duplicates of the first two attributes and should be ignored.

1.17 *Viewing response time or hit rate reports for a URL Test

To view reports after a URL Test execution, be sure not to edit the name of the test suite in the editor.

If you choose to view response time and/or hit rate reports for a URL Test, the reports are created and stored in a project folder as .html files. These files are not visible in the Test Navigator view, but they are visible in the Navigator view. To access them from the Navigator view, you can switch to the Resource perspective or you can add the Navigator view to the Test perspective by selecting Window->Show View->Other from the menu bar, expanding Basic, and then selecting Navigator and OK. If you double-click on one of these files to open it, by default it opens in Page Designer. To view the report, close the .html file in Page Designer and instead open it by selecting Open With->Web Browser from its context menu in the Navigator view.

Note: This has been fixed in V6.0.0.1.

Return to the main readme file