Plan
Plan
1. Load test
2. Endurance test
3. Spike test
4. stress test
5. volume
RAM: At least 16Gb RAM, 32GB recommended. Avoid using more than 50% RAM.
https://jmeter.apache.org/
How To install
===============
-download -> unzip -> bin -> jmeter.bat
*Do not use GUI mode for performance test, debug and setup
Start JMeter
Client-------------JMeter------Server
TestSite:
=========================================
https://reqres.in/
https://lifecharger.org/books-i-am-reading/
Jmeter: website
https://reqres.in/api/users/2
====================
Creating JMeter test
=====================
-Start JMeter
-Test plan creation
-Thread group
-Sampler (http)
-Listener
-Run
Listener
=============
-view results in tree
-Aggregate report
-Graph results
-Simple data writer
Assertions
===========
Response assertion
Duration assertion
size assertion
html assertion
XML JSON assertion
XPATH Assertion
Learn Blazemeter
=================
GUI consumes memory, slower
Integrating with any external process CI/CD
I’ve completed performance test on frequently used API for test App.
Test executed for the below mentioned scenario in server 000.000.000.00.
200 Concurrent Request with 10 Loop Count; Avg TPS for Total Samples is ~ 234 And
Total Concurrent API requested: 1400.
300 Concurrent Request with 10 Loop Count; Avg TPS for Total Samples is ~ 350 And
Total Concurrent API requested: 2100.
400 Concurrent Request with 10 Loop Count; Avg TPS for Total Samples is ~ 424 And
Total Concurrent API requested: 2800.
500 Concurrent Request with 10 Loop Count; Avg TPS for Total Samples is ~ 443 And
Total Concurrent API requested: 3500.
While executed 500 concurrent request, found 82 request got connection timeout and
error rate is 0.23%.
Summary: Server can handle almost concurrent 3200 API call with almost zero (0)
error rate.
Please find the details report from the attachment and let me know if you have any
further queries.
Test purpose e 5 or 10 thread is okay, but don't give more. And keep the ramp up
within 10 sec.
3. Increase the load as long as the error rate is less than one percent. By this
you did load test
4. Keep this load for 10 min under threshold which you have found in step three and
by this you achieved endurance test.
5. All of a sudden increase the load beyond load and check how the system behaves
and by this you did spike testing.
You can run from non GUI mode and make a report.
My question is why do you have to wait for my / our assignment to try what you have
already learned?
Why don't you guys test yourself and do some project on your own?
Now that i have given you all some idea i hope you will keep using what you have
learned and explore more. Don't stay stuck, take help from anyone you see out there
but I repeat don't stay stuck.