You can quickly create a load test from an API definition file. You can use WSDL, OpenAPI, Swagger, and WADL files:
-
Select File > New > Load Test.
– or –
On the Dashboard, click Load Test on the New Test tile:
-
In the New Load Test dialog, select the API Definition option and click Start.
-
Select how to input your API definition. You have two options:
-
File
- Enter the file path or URL of the API definition in the field provided.
- Alternatively, click the Browse button to locate and select the file from your computer.
-
SwaggerHub Integration
- Import an API definition from SwaggerHub. This option is available if you've integrated ReadyAPI with your SwaggerHub account. For more details on integration, see the SwaggerHub integration page.
-
Select one of the following options:
- My API: Search for and select an API from your private SwaggerHub account.
- Public API: Search for and select an API from publicly available APIs on SwaggerHub.
Tip: Use the Filters button to refine the API list:
- Select specific API specifications: OAS2, OAS3, OAS3.1, AsyncAPI, or All.
- Optionally, select Private or Public for My API.
- Click Select All or Deselect All to manage your filter selections.
Click Next.
-
-
Select the load template to use. If you are not sure which one to pick, select a baseline template and click Configure Load Test.
-
Configure the load test:
-
Specify the name of the load test in the Load Test Name field.
-
Specify the number of virtual users simulated in the test. Each virtual user will send a request to the service. For more information on how ReadyAPI simulates virtual users, see Load Type.
-
Configure load test assertions. If you are not sure, specify the recommended values or select the Skip assertions for now checkbox to configure assertions later.
-
Click Finish.
-
-
After you create a load test, ReadyAPI will offer you to run it, or configure it to run on multiple machines. Select one of these options to continue working with the created load test.
For more information about running your test on multiple machines, see About Distributed Load Testing.