We all want software to run as fast as possible, and performance testing can help make that happen. But often, it's the steps before and after the testing that don't get nearly the focus they should. As a result, performance issues might get missed during testing, or they might not get properly fixed if they are identified…or they might even creep back in later during another development cycle.
To get past that, it often helps to think of performance as an entire process, instead of just a series of tests. For this session, we’ll go into detail about the “Before”, “During”, and “After” phases of this process. We’ll cover what kind of questions that should get asked before any tests even start, how to adjust during the testing phase when the unexpected happens, and after tests are done, what can be done to leverage those results and put those lessons learned to use for the future.
