Below are some recommendations that will help you avoid issues when creating and running test recipes.
After installing ReadyAPI TestServer, we recommend that you:
Configure TestServer settings.
Inform your IT department about having installed the product so that firewalls and proxies running in your network do not consider TestServer as a spammer.
Before executing a test recipe, make sure ReadyAPI TestServer is running.
TestServer does not start automatically when you launch your computer. You need to start it manually. See Running and Configuring TestServer.
Before sending a recipe to TestServer, make sure you specified the user name and password to connect. See Running Test Recipes.
Tests run on ReadyAPI TestServer have a number of limitations. For example, for security purposes, Groovy scripts cannot create class loaders. Otherwise, it would be possible to execute malicious code on TestServer. For information on possible security risks and test recipe limitations, see Security Considerations.
To refer to a property, use the same syntax as you do in the ReadyAPI user interface:
The default names for the test steps are GET request 1, DataSource 1, and so on. For convenience, we would recommend that you do no use default names, but specify descriptive names for the test steps that you create.
If your recipes require other files, for example, attachments or SSL keystores, you can put these files to a folder and allow ReadyAPI TestServer to access it by setting the allowed.file.paths property. Otherwise, you will need to send another POST request with the files. See Providing Files for Tests (text-based recipes) and Data-Driven Recipes (code-based recipes).
If you are sending test recipes to TestServer from ReadyAPI, duplicate the
$ symbol in the property expansion expression: