Would you like to minimize risks of failure on your system when implementing changes?
The Figaf Integration Regression Tool enables you to make sure you test enough. IRT makes is easy to set up test cases based on productive messages from your test system. Simply select an ICO — IRT will let you record the next 5 messages on the ICO, and save it as a test case. On your test system you can then create the same setup and perform the test again. This allows you to confirm that the changes do not affect the adapter modules you have on your system, routing options, and operation mappings.
How to use?
|Business Test||Developer Test||Mapping Test||Figaf IRT||Tool 1|
|Test backend functionality||x||–||–||–||R|
|Test all adapters||x||x||x||x||–|
|Test routing of messages||x||–||–||x||–|
|Set up new test cases||+||+++||+++||+++||++|
|Price per test||+||++||++||+++||+++|
|Validation of result||+||++||+||+++||+++|
|Perform complex test||++||++||++||+++||+++|
1) Int4 Regression Interface
R) Receiving Only
How it works
- To be able to record messages in the modules, IRT adds a module as the first module on the Sender communication channel and last on the Receiver Communication channel. This is the Agent Module.
- When the user from IRT wants to record a number of productive messages, IRT sends a command to a web service on the agent system, along with the information that the specific interface should record the next e.g. 5 messages.
- The Agent Module will then verify if the message coming through should be saved, and if it should be saved, it saves the message to the JMS queue. It also marks the message to be saved by adding a dynamic property to the message.
- When the messages receive the Receiver Agent Module, the file is saved again as the result of the message. There can be multiple outputs of an input message.
- The JMS queue is picked up by the test system of IRT.
To perform tests
- You select the ICO you want to use for the testing.
- The user can specify which elements should not be compared using Xpath so e.g. time changes are not counted as errors.
- To test a message the user selects one or more test cases.
- IRT then sends the messages through the XI30 channels it has created, records the output for the message, and makes it the test result.
- After the test is performed, the user will be able to see the result.