One thing that comes to mind is TruClient. It's great for emulating real user behavior on an application, especially when you need to consider how the application interacts with the browser UI. It's like using a UFT script but directly within the browser. However, the challenge is that TruClient can be very memory intensive. In most cases, clients' infrastructure simply can't handle the resource requirements for running extensive TruClient tests. Ideally, there would be a way to address this memory bottleneck. We encountered a situation where a simple request-response test with HTTP wouldn't suffice. The user interaction involved a browser layer that needed to be factored in for realistic testing. If OpenText could find a way to work around the memory issue, that would be very helpful. Here's why: sending a request and getting a response from the server is one thing. But users also want to consider the additional layer of the browser interacting with the application. To make the test as realistic as possible, you need to test it with different browsers. And to do that with multiple browser windows open, you really need a protocol that addresses this capability. It exists, but most clients can't handle the resource requirements for running such tests.
