🏋️Load Test
Load Testing is a vital form of performance testing used to assess how a system behaves under expected user loads. The primary objective is to verify that the application can handle a specified number of concurrent users, transactions, and data volumes without experiencing slowdowns, crashes, or failures.
By simulating real-world usage conditions, load testing helps uncover performance bottlenecks, scalability limitations, and other potential issues that may impact the user experience. It ensures that the system meets predefined performance benchmarks and remains stable and responsive under pressure—making it an essential step before deployment to production environments.
To get Started with Load Testing you should select the Load Test icon from the side menu bar in Dashboard page. Upon clicking it will direct the user to Load Test page.
Select Application
Select the Application which has been created from Application page in Application Dropdown, the selected Application can be WEB APPLICATION or REST API Application for which user wants to perform Load Test.
Adding Test Case
When an application is selected, users have the option to add a new test case by clicking the Add Test Case button. They can fill in the input fields and then click the Save button to store the load test data in Testwheel. Once saved, users have the privilege to perform Edit and Delete actions for the created test case.
Adding Authorization
If needed, users can input authorization details by navigating to the Authorization tab. They can then select the type of authentication and enter the credentials into the provided input field. By default, the CSRF Token toggle is Disabled. Once the user activates the CSRF Token toggle switch, they can input the token value into the designated input field.
NOTE: To Load Test a CSRF enabled site, the first URL provided must be of Home page or sites Landing page.
The Second URL should be for Login and must have an authorization type selected as Basic Authentication with username and password and CSRF must be enabled.
All the remaining test URL must be added below the second target URL only.
In case of any failure in the above-mentioned steps would result in test failure for all the target URLs for the particular testcase.
NOTE: Editing the first and second target URL of the CSRF enabled testcase is not recommended.
Disabling the CSRF Token of the second target URL is strictly not recommended because it would result in entire test case failure.
If needed then the second request username, password and CSRF token name can be updated but the authorization type must not be changed from Basic Authentication to none under any circumstances.
Last updated