IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Testing modules > Unit testing
Limitations for the integration test client
From time to time, you may encounter some limitations in using the integration test client. In most situations, you can successfully work around these limitations.
Some known limitations are:
- Null pointer exception (NPE) when testing in Business Process Choreographer Explorer and Web Services Explorer
- Duplicate names in an XSD not supported in the test client
- The Save Resource window does not contain a Cancel button
These limitations are discussed in the following sections.
Null pointer exception (NPE) when testing in Business Process Choreographer Explorer and Web Services Explorer
After testing an application in the integration test client no errors may be shown; however, when the application is deployed to the server and tested in the Business Process Choreographer Explorer and the Web Services Explorer, it can still result in a null pointer exception (NPE).
The integration test client has different behavior than the Business Process Choreographer Explorer and the Web Services Explorer. The test client is used to unit test the components, so by default, they are sending empty strings for the data for all of the values that you leave blank.
In comparison, Business Process Choreographer Explorer and the Web Services Explorer are sending in data only when you specify it, null or otherwise. Many of your rules or code might be accessing items that are null or undefined, resulting in errors.
During the integration test, if you receive a null pointer exception in the root exception stack, check to see if the data that was passed in (or received) is a null value.
Duplicate names in an XSD not supported in the test client
This limitation is only applicable in cases where an XSD for a business object is created outside of the business object editor. (The editor will not allow you to create an XSD that exposes this limitation.)
The limitation manifests itself when using the test client to enter values into a business object based on an XSD that contains duplicate names. When the business object is created you will notice that all values belonging to elements with the same name, except for the last one, will be null by the time the business object is received by an operation.
This limitation results from the way that business objects are created internally. Since each property is stored by name, duplicate names are not allowed.
The solution is to ensure that XSDs created outside of the business object editor have no duplicate names.
The Save Resource window does not contain a Cancel button
When you close the integration test client, a Save Resource window opens to ask you whether you want to save your changes. This window only contains a Yes button and a No button. Regardless of which button you select, the integration test client will close. Due to a limitation of the Eclipse framework, the Save Resource window does not contain a Cancel button that would enable you to cancel the window and keep the integration test client open.