Scribd
Upload
18 views4 pages

Non-Functional Testing Techniques Guide

1) Performance testing involves testing the stability of an application under various workload conditions through load testing, stress testing, endurance testing, scalability testing, and volume testing. 2) Load testing tests the application with expected and peak user loads over durations of 1 hour by varying the number of concurrent users. 3) Stress testing checks the breaking point of an application by steadily increasing the number of concurrent users over 1 hour durations.

Uploaded by

sambap954
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
18 views4 pages

Non-Functional Testing Techniques Guide

1) Performance testing involves testing the stability of an application under various workload conditions through load testing, stress testing, endurance testing, scalability testing, and volume testing. 2) Load testing tests the application with expected and peak user loads over durations of 1 hour by varying the number of concurrent users. 3) Stress testing checks the breaking point of an application by steadily increasing the number of concurrent users over 1 hour durations.

Uploaded by

sambap954
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Non - Functional Testing:

1) Performance testing 2) Usability 3) Accessibility 4) Security 5) Compatibility

Performance Testing:

Testing the stability of the application under various workload conditions.

Types

1. Load Test:
Testing the application with the expected user load.
Concurrent user: X users Duration: 1 hr.
@ New Application: Assumption (Stakeholder/BA)
@ Existing application: Production log analysis
Tools: Dynatrace / Appdynamics / Google analytics
# Peak Load Test:
Test the application with the peak load condition. (Weekly / monthly pattern)
Concurrent user: Peak load (big bill - last yr.) Duration: 1 hr.

2. Stress Test :
To check the breaking point of the application
Concurrent user: X, 2X, 3X users Duration: 1 hr.

3. Endurance Test / Soak Test :


Testing the application for a longer period of time to check the memory leak.
Concurrent user: X users Duration : 4 hrs

4. Scalability Testing :
Testing the future load with the current infrastructure
Concurrent user : Future Load Duration : 1 hr

5. Volume Testing :
Testing the scenarios which are having heavy interactions with the database.( insert/update)
Concurrent user : X users Duration : 1 hr
PTLC:
NFS

Test Plan

Test Design (Scripting)

Test Execution (achieve throughput in NFS )

Test Result Analysis (Report)


Benchmarks &
Recommendations
Throughput: no. of transactions in an hour.
Scripting:
1. Static Value --- > Parameterization
Username & Password
2. Dynamic Value  Correlation
Base lining vs. Benchmark:

Pre-requisites for installing Jmeter


1. Latest version of apache Jmeter
2. Install Java JDK
3. Setup JAVA_HOME & path
4. Port opening ( firewall exception )
5. Browser proxy edit access
6. Jmeter certificate installation.

To Create / Record a Script in Jmeter:


1. Pre-Req: disable firewall & anti-virus (search – windows firewall – off )
2. Import the root certificate to the browser ( before 5.2)
 Import into browser (settings->manage certificates -> browse & add from C path:
C:/Apache Jmeter /bin/certificate )
3. Setup a Proxy server ( address : localhost/Ip address, port: 8888 )
 If company already has proxy setup, then no need for new setup. Just configure that
existing port in Jmeter.
WHY we need to setup PROXY SERVER:


---
4. Configure JMeter tool to capture HTTP traffic.
5. Record the script
6. Execute the script.

Troubleshooting steps: In case recording is not working.


1. Disable Firewall
2. Disable Anti-virus
3. Clear browser cache and cookies

Jmeter topics:

1. Elements
2. Controller
3. Sampler

1. Elements:

Test paln --.> add - >

1. Threads
2. Config element (user def var ) --------------helps to run jmeter perfectly
3. Listener ----------------------------------------- visualize test results and debugging
4. Timer
5. Pre-Processors ----------------------------- execute some things
6. Post-Processors ----------------------------- process response
7. Assertions ------------------------------ define check points, response code
8. Test Fragment-------------------------------- module controller
9. Non –Test elements ---------------------------create mirror server

You might also like