Load Test Automation

TABLE OF CONTENTS

1. Overview

2. Prerequisites

3. Performing the Load Testing 

3.1 Creating a Project Page and Configuring the Spreadsheet 

3.2 Schedule and Execute the scripts using algoQA non web enabled version

3.3 Limitation

1. Overview

Load testing is a type of performance testing used to evaluate how a system or application behaves under a specified load.

2. Prerequisites

Java-JMETER is a performance testing framework that uses Java. It supports Java version 1.8 or higher To Install Java, click here.

3. Performing the Load Testing 

3.1 Creating a Project Page and Configuring the Spreadsheet 

1. On the Main Canvas, navigate to the Create Project Page.
2. In the Create Project Page, enter the Project Name, select the Automation type as Load Test Automation and click Create Project button. 
3. Let us configure the spreadsheet which will serve as an input file. 
4. For Configuring a spreadsheet, use the parameters defined in the following table:
   
   

   Parameter	Description
   Name	Load Testing
   Type	API
   URL	HTTPS://staging.algoshack.net
   Thread Count	5
   Loop Count	1
   Ramp Up	5
   Set Duration	6
   Infinite Loop	FALSE
   End Point	User/Login
   Method	POST
   Request Body	{"user":{"email":"eipgctzmvsfivtnkkx@tmmcv.com"," password":"eyJhbGciOiJIUzI1NiJ9.UkBqZXNoMTIz._pUSOKQleRDRgb0XzNT1cY3UVFBVdMzYjB_0iZb7NAM"}}
   Headers	content-type:application/json
   Authorization	NA
   Store Variable	accessToken

   
   
5. Navigate back to your project and click the Configuration File to select Upload. Upload the configured spreadsheet.
6. Rename the file with the same name as Project Name provided and save the changes. A sample configuration spreadsheet is attached for your reference.
7. Configure a node  with features and UI elements on the Main Canvas and Click OK to add the configuration and then click Close button.
8. Next, let us generate test cases.
9. In the Main Menu, click Generate button to generate test cases..
10. Test Cases are generated successfully. Click the OK button.
11. Expand the test cases folder to view the test cases inside the feature files.

12. Click the txt file to view the test cases.

13. Download the latest test cases by clicking on More Menu options (three dots) and then selecting the Download button.
14. Navigate to the Downloads folder, click the Zip file, extract the contents of the zip file and select the appropriate folder..
15. Next, let us perform execution of the scripts.

 3.2 Schedule and Execute the scripts using algoQA non web enabled version

Make sure you have downloaded algoAF from the Downloads section. For more information, see Installation steps for algoAF and Setting up algoAF.

Perform the following to launch algoAF and update the settings:

1. Open algoAF and click the Settings icon available at the upper-right corner.
2. In Code Generator Settings pop-up window, select the Application Type as Load Testing, language & Framework as Java-JMeter, click the Update button and close the pop-up window.
3. Reopen the algoAF and click the Upload Test Cases button.
4. From the extracted folder select both the files and then click the Open button. 
5. Test Cases are uploaded onto algoAF.
6. Click the Go button to generate scripts.
7. Test scripts Generated successfully and ready for execution and click the OK Button
8. Click the Schedule & Execute button.
9. Enter test case ID in Test Suite textbox and click the Confirm button to start the execution.
10. When the execution kick starts, wait until the execution is completed until you see Build Success message on algoAF console.
11. Click the Reports button to view the execution reports.
12. Click the Refresh button and then scroll to right side and click the Details link to view reports.
13. Screenshot represents the JMeter reports. In this report, click the first API in the Modules column.
14. Click the first HTTP Request in the Test Case(s) column.
15. In the detailed information section, you can view the Result, Status code and Response Data.

 3.3 Limitation

Ensure that the spreadsheet is configured exactly as shown in the attached sample spreadsheet. Any deviations from this configuration may lead to inaccurate results or issues during the process. Refer to the sample spreadsheet for appropriate configuration.