Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rahulchandradasrcd/rest-booking-api-performance-testing-using-jmeter
https://github.com/rahulchandradasrcd/rest-booking-api-performance-testing-using-jmeter
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/rahulchandradasrcd/rest-booking-api-performance-testing-using-jmeter
- Owner: rahulchandradasrcd
- Created: 2024-10-29T17:16:06.000Z (2 months ago)
- Default Branch: master
- Last Pushed: 2024-10-29T18:00:21.000Z (2 months ago)
- Last Synced: 2024-10-29T20:09:31.711Z (2 months ago)
- Language: HTML
- Size: 3.71 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Rest-Booking-API-Performance-Testing-Using-JMeter
This project demonstrates Performance Testing using JMeter, providing a collection of tests to validate various endpoints of the API.
## Features
* Tests for GET, POST, PUT, DELETE requests
* Collection of tests covering different API endpoints
## Technology used:
- JMeter
## Overview
This repository contains a JMeter project for performance testing of the [Restful-Booker](https://restful-booker.herokuapp.com/apidoc/index.html) Website.
## Usage
1. Clone the repository to your Local Machine From:
````
https://github.com/rahulchandradasrcd/rest-booking-api-performance-testing-using-jmeter.git
````
2. Open JMeter and load the test plan.
3. Configure the necessary settings and parameters in the test plan.
4. Run all Test plan.
## Run in CMD (Non GUI mode) on your project folder
1. To run the test plan through CMD (Non GUI mode), use the following command:
````
jmeter -n -t Test_100.jmx -l report\Test_100.jtl
````
This command runs JMeter in non-GUI mode (-n), specifies the test plan file (-t), and writes the results to a JTL file (-l).
2. To run the test plan through CMD (GUI mode), use the following command:
````
jmeter -g report\Test_100.jtl -o report\Test_100.html
````
This command runs JMeter in GUI mode (-g), making report to htl file (-l), and writes the report results to a html file (-l).
## Testing
The sample test plan includes the following components:
1. Thread Group:
* Thread Count: 10
* Ramp-Up Time: 10 second
* Explanation:
* Thread Count: Represents the number of virtual users (threads) executing the test concurrently.
* Ramp-Up Time: Represents the time taken for all threads to start executing.
2. HTTP Proxy Server:
* Used for recording the script of sample pages.
3. Logic Controllers:
* Loop Controllers:-
* Loop Count: 01
4. Config Eelements:
* http header manager
* json extractor
5. Listeners:
* view result trees
* summary report
* aggrigate report
6. Save and Run the test plan
7. Execution:
* Run all the test plan sequentially
* you can start your execution with 100 thread group until error rate is 1.0%
8. Point to explore:
* Running through CMD (Non GUI mode).
* Running through CMD (GUI mode) for generating html report.
## Report
1. 2000 Concurrent Request with 01 Loop Count; Avg TPS for Total Samples is ~ 200 And Total Concurrent API requested: 12000.
2. 2500 Concurrent Request with 01 Loop Count; Avg TPS for Total Samples is ~ 121 And Total Concurrent API requested: 15000.
3. 2600 Concurrent Request with 01 Loop Count; Avg TPS for Total Samples is ~ 260 And Total Concurrent API requested: 15600.
4. 2700 Concurrent Request with 01 Loop Count; Avg TPS for Total Samples is ~ 217 And Total Concurrent API requested: 16200.
5. 2800 Concurrent Request with 01 Loop Count; Avg TPS for Total Samples is ~ 195 And Total Concurrent API requested: 16800.
6. 2900 Concurrent Request with 01 Loop Count; Avg TPS for Total Samples is ~ 157 And Total Concurrent API requested: 17400.
### While executed 2900 concurrent request, found 3160 request got connection timeout and error rate is 18.16%.
### Summary: Server can handle almost concurrent 16900 API call with almost zero (0) error rate.