HTTP Test

Step 1: Test Setup
This screen allows user to create POST, PUT, GET and DELETE request via web editor. Every HTTP request type has its own configuration screen as follows:
GET Request
Name: It’s the name of the request. It’s a mandatory field.
URL: URL or End-point of the service. It’s a mandatory field.
Response Timeout, Connect Timeout: As they are not necessary for every request. They can be left blank in case unknown. In case they are set to some specific values, they will be used as an assertion for request. In case those values are reached during test execution, request will be marked as failed.
Header Name, Header Value: They must be set according to your request. In case unknown, they can be left blank.
POST Request
Name: It’s the name of the request. It’s a mandatory field.
Request URL: URL or End-point of the service. It’s a mandatory field.
Response Timeout, Connect Timeout: Those values will behave as an assertion for your request. They are not mandatory for every request and can be left blank in case unknown.
Header Name, Header Value: They must be set according to your request. In case unknown, they can be left blank.
Body: You should enter the payload/message you want to send to your request in that field.
​
PUT Request
Name: It’s the name of the request. It’s a mandatory field.
Request URL: URL or End-point of the service. It’s a mandatory field.
Response Timeout, Connect Timeout: Those values will behave as an assertion for your request. They are not mandatory for every request and can be left blank in case unknown.
Header Name, Header Value: They must be set according to your request. In case unknown, they can be left blank.
Body: You should enter the payload/message you want to send to your request in that field.
​
DELETE Request
Name: It’s the name of the request. It’s a mandatory field.
Request URL: URL or End-point of the service. It’s a mandatory field.
Response Timeout, Connect Timeout: Those values will behave as an assertion for your request. They are not mandatory for every request and can be left blank in case unknown.
Header Name, Header Value: They must be set according to your request. In case unknown, they can be left blank.
Step 2: Basic Settings
You need to configure those parameters before starting your performance test.
Engine Count: This parameter let you create engines on Loadium’s server aligned with its subscription type. The parameter is 1 by default. You can change your subscription type by going to this web site.
Thread Count: This parameter let you define thread number to create in each Engine generated. Maximum thread count per engine is 500 by default.
Ramp Up Time: This parameter let you define the total time for all Threads to start. Example: In case you have 500 threads and 10seconds ramp-up time. For every second, 50 thread will be generated by Loadium.
Iteration: This parameter defines the number of iterations for every threads to execute the test scripts.
Duration: This parameter defines test time for Loadium to execute. Textbox or sliders can be used to manipulate those values.
✏️  Note: Test execution time of a script is defined by Duration or Iteration parameters. In case not all iterations are completed during the defined “Duration”, test execution will stop. Same rule apply vice versa. If all “Iterations” are completed before defined “Duration” test will stop.
Step 3 : APM Tools
Loadium is integrated with Application Performance Monitoring tools. As of today, Loadium is integrated with New Relic and App Dynamics. You should provide New Relic API key or App Dynamics’s credentials to Loadium. By doing so, you’ll be able to select which components and its metrics to monitor during test execution.
More than one APM tool can be added to a performance test. You may find detailed information on APM Integrations page.
Enjoy load testing!
Getting Started with Loadium
Load Test Metrics
Sandbox
Pricing
If you don't see the answer to your question here, please reach out to us to let us know! We're always improving our documentation.