Besides being able to run your tests from your local machine, APId also has the functionality to run from around the world. This functionality is powered by the APId cloud offering.
The cloud offering works pretty much the same way. You need to define your transactions, as you would with the CLI, and then using the APId CLI issue a
remote command. This works as follows:
The CLI reads the transactions from the specified directory or file, as per ususal
It will execute each transaction, sending the necessary
STEP information to the cloud for remote execution
It will wait for each
STEP result to come back and continue with the other steps and transactions
One major benefit of this workflow is that all the interpolation is done locally (on the machine running the CLI), thus you have control over the environment it runs in. This means you can invoke any custom executables.
In order to use the power of the cloud you will need a personal access key. To generate one, you will have to:
Head over to https://www.getapid.com and sign up
Go to the dashboard and create a new access key
A reference on how use the CLI after installation for remote execution can be found here.
APId cloud runs in multiple regions worldwide. Below is a list of the current ones. The default region is set to Washington.
The execution timeout is set to 30 seconds. If your API does not respond within that time an error is returned.
We've tried making the billing model as simple as possible. Each account has a quota of units they can use each month for running their tests on the cloud infrastructure.
Each unit corresponds to 100ms of execution time of a step - thus the response time of the API for each step.
You are not billed for any interpolation or step preparation (which is done on the machine you're running the CLI on).
API response time