Can your product handle a tsunami ?
From my experience as a consultant working on various projects, I observed that application performance is often not treated as a first class citizen until just before release.
How do you anticipate the number of people using your application at any point of time ? How would you handle a surge in the the user traffic ? How would you know the limits of your system just before it breaks down ?
In a true agile environment, where the team believes in fast feedback and continuous quality delivery, we need to treat performance tests just like any other functional tests. In this talk I will be sharing my principles and taking you through the various aspects the team may consider for the application's performance.
To some capacity everyone can have valuable inputs to understand performance of the system. I am intending to keep this talk less technical so that people from various capabilities can join and get an insight.
Outline/Structure of the Talk
I will be touching upon the following and how each of that can be applied in an agile environment.
- Why performance testing
- What is Load and stress testing
- The agile way of performance testing
- Frontend and Backend performance testing
- Performance test pyramid
The participants would take away:
- Significance of performance testing
- Things to consider for performance testing
Developers, testers, Operations, Product owners