Scott Barber, one of the gurus of “Performance Testing”, has given a training subjected performance testing strategies and good practices on 2-3rd of June as a guest trainer of Keytorc Software Testing Services in Istanbul. During the training, he has mentioned about his experiences exceeding 15 years and good practices related to performance testing. Besides technical details, he focused on value adding strategies and ways of realizing successful performance testing projects.
Here you can find few tips, mentioned in the training.
- Initial step for performance testing is asking right questions and avoiding getting right answers to wrong questions.
- Performance testing must be defined in and followed properly according to SDLC. Thus, legacy and new system’s performance can be measured objectively. By the way, in case of performance bootlenecks, root-cause analysis might be done rapidly.
- Performance testing efforts should start at the beginning of a project, otherwise there won’t be enough time to analyze and tune towards the end of the project.
- There is no “One size fits all” strategy for performance testing. According to context, it should be adjusted.
- Everybody is responsible for performance. Insufficient performance can be avoided by 15 minutes of daily efforts.
- Always have PoC on your own test environment, on your real applications. Thus, sales demo does not make any sense at all.
- It is not always required to use different test tools to test different platforms. Many times, it can be handled with existing performance testing tools.
- Adopt your plans to your results.
- T4APM: The T4APM approach hinges on applying a simple and unobtrusive “Target, Test, Trend, Tune” cycle to tasks in your application lifecycle—from a single unit test through entire system production monitoring.
For more information visit our website: https://www.keytorc.com/