Lessons Learned From 60 Days of Performance Testing - Kim Knup
9th November 2017
-
Locked
Kim Knup
Senior Quality Engineer
Talk Description
Imagine the following scenario.
You have a new commerce platform and you have just proven that it performs just as well as the old one.
As a team you have a goal of selling a certain number of items over a very specific time period and by using the current knowledge and data you have, you confirm this will not be a problem… until you receive a clearer picture of how the data will be structured and it becomes clear within 10 seconds that the system will not scale as expected.
What now?
Takeaways
- Why did we need performance testing and how it helped us
- What are different types of performance tests we chose to employ
- Why we learned to vary our performance testing strategy
- The importance of understanding our production data volumes and throughput
- The importance of understanding our real end-user’s behaviours
All of the above feed into helping you create a performance testing strategy that can not only help you gather information of your system under stress but also help your testing strategy in general.
Kim Knup
Senior Quality Engineer
She/her
Kim is Senior Quality Engineer and co-organisers of the Brighton tester meet-up.
Sign in
to comment
Suggested Content
Create, run, and maintain web and mobile tests with no-code, AI-driven automation in the cloud
Explore MoT
RiskStorming; Artificial Intelligence is a strategy tool that helps your team to not only identify high value risks, but also set up a plan on how to deal
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community