Date post: | 19-Feb-2017 |
Category: |
Technology |
Upload: | sebastian-hensiek |
View: | 87 times |
Download: | 0 times |
Maharshi ShahTestingDiaries.c
om
Rich FriedmanRedLine13.com
Why Performance Testing?
Source: http://bit.ly/WhyPerfTest
Some Statistics
47% of consumers expect a web page to load in 2 seconds or less.
40% of people abandon a website that takes more than 3 seconds to load.
A 1 second delay in page response can result in a 7% reduction in conversions.
If an e-commerce site is making $100,000 per day, a 1 second page delay could cost $2.5 million in lost sales a year.
Performance Testing is Must When…
High load is expected on application.Application has large volume of data.Application is sluggish.Customer requests it.
An Example Project
Scope: Home page, login, search, view profile, edit profile, article listing, article details, logout.
Goal: To assess that the system is able to support 4000 users with response time less than or equal to 5 seconds.
Additionally, stress testing is to be done to determine system’s preparedness for high load.
Minimal or no errors during all tests.
What is Performance Testing?
Non-functional testingPerformance testing: To validate speed,
scalability and stability.Load testing: To check application behavior
under normal and peak load.Stress testing: To evaluate application when
it’s pushed beyond normal conditions.Special mentions: Volume testing, spike
testing, endurance testing.
Usual Performance Testing Architecture
Performance Testing Approach
Gather requirements.Prepare a plan.Select a tool.Prepare and run your performance script.Scale your tests if required.Analyze results and prepare a report.
Requirements Gathering
Number of usersExpected response timeEnvironment and test machines setupBusiness critical scenarios to performance
testTest data
Preparing Test Plan
Prepare a plan which outlines your performance testing approach.
Get it reviewed and approved from client.
Tool Selection
Running and Scaling Tests
Prepare your script and execute it for large number of users.
Monitor server resource consumption while test is running.
Use cloud based services like RedLine13 to scale your performance tests.
Analysis and Reporting
Keep target audience in mind while reporting.
Provide detailed analysis based on your observation.
Try to pinpoint performance bottlenecks and suggest ways to mitigate them.
Provide technical details such as throughput, resource utilization, test parameters etc.
Report errors if found.
Performance Testing Best Practices
Test environment should be identical to production environment.
Application should be functionally stable.Monitor server resources consumption.Try to mimic the real world scenarios.
Thank You
Q&A
Contact Info
Testing DiariesEmail: [email protected]: http://www.testingdiaries.comFacebook: https://www.facebook.com/TestingDiariesTwitter: @Testing_Diaries
RedLine13Email: [email protected]: https://www.redline13.comFacebook:
https://www.facebook.com/redlineloadtestTwitter: @redlinethirteen
R