This topic explains how you can use SOAtest to monitor transactions that pass through a TIBCO EMS system, then generate functional test cases that check the monitored messages.
Another way to create tests is to have SOAtest’s recording proxy monitor traffic at one or more JMS, HTTP, or MQ endpoints as an application is exercised. SOAtest "listens" to traffic requests and responses, then builds a traffic file of legitimate request/response pairs. This traffic is then used to generate a test suite that represents the captured behavior in preconfigured SOAP Client or Messaging Client tools. See 記録した HTTP、JMS、MQ Traffic からのテスト作成 for details.
SOAtest can monitor transactions that pass through TIBCO EMS, then generate functional test cases that check the monitored messages. In addition to providing visibility into the system’s messages, this allows you replay transactions directly from SOAtest and verify that the monitored functionality continues to work as expected.
To achieve this, you tell SOAtest how to connect to your TIBCO EMS and what destination (topic or queue) messages you want it to monitor, then you prompt it to start monitoring. SOAtest will generate a test suite of Messaging Client tests for each JMS message captured at the specified destination or for all messages within the process flow (if a process tracking topic was used). These tests are preconfigured with the connection parameters, requests, and destination information so that SOAtest can replay the same messages.
SOAtest can generate test clients for the following types of JMS messages:
The tibjms.jar file must be added to your classpath (via Parasoft> Preferences> Parasoft> System Properties).
To generate tests:
If you want SOAtest to use the JMS QueueBrowser API in order to trace messages posted on a JMS queue— without removing them from the queue— enable the Leave messages on the queue option. This allows SOAtest to gain visibility into these mes-sages without impacting the transaction.
For a discussion of potential complications with this option—and how to avoid them—see JMS Queue Options.
In addition to automatically generating functional tests from monitoring the transaction messages that touch JMS endpoints in TIBCO EMS, you can also visualize and trace messages that take place through EMS as part of the transactions that are triggered by the tests, and then dissect them for validation.
For details on how to do this, see Event Monitoring for ESBs, Databases, and other Systems.