What you need is an easier way to track all the activity that occurs during a test and set markers for invalid conditions.
TestBench offers a method of tracking pretty much everything. From database effects to job log messages. From data queues to data areas. From program calls to IBM MQ traffic.
That puts the focus on the the program linkages and the parameter values must be verified or populated.
That’s just the start. Why not track program calls through submitted jobs, even submitted jobs which submit other jobs? And for every call see the vital performance data so you can identify potential improvements.
Testing such applications is a challenge. It is very difficult to view the traffic sent/received on a queue and data can be hard to understand.
This is a vital area of testing as without detailed monitoring it is impossible to know whether all the traffic has been sent and whether all the sent traffic has been received and correctly processed.
We believe we offer one of the most capable file compare utilities elegantly handling large data volumes and high field counts.
Report comparison is a much trickier proposition as the data is only partially structured and is represented in multiple data structures. TestBench includes a unique solution that can save hours.
IBM i batch processing is core to your applications but testing it is tough.
For the first time you can access every aspect of a program execution and set automatic invalid state markers.
Combine our batch testing capabilities with UI automation or manual testing to see what really happened during a test.