TestServer technically is a REST API wrapped around the Ready! API solution. That allows our users to interact with it in a more dynamic way.
There are two common uses for TestServer:
1. Developers would write code to dynamically generate and process Ready! API tests. This would allow the developers to use the Ready! API platform without installing additional software. This would also allow developers to integrate other test frameworks like Cucumber, JUnit, etc to use our engine for testing their APIs
2. TestServer can be the central runner for all SoapUI tests. This requires a central TestServer to be available on the network, and then you can use that as an engine to run the tests and give you pass/fail results. That way you don't have to install Ready! API on everybody's machine. You also would not have to install and activate every node for your CI machine that would run SoapUI NG in headless mode
Let me know if you have further questions. Thanks,
Mike
