Black Tea Testing #2 - Performance testing: why? when? how?
Download as PPT, PDF1 like506 views
Performance testing is crucial for small and big startups to validate their ability to handle customer loads and maintain product quality. The testing process should occur at various stages of development and requires the selection of appropriate tools, preparation of the testing environment, and careful analysis of results. Key steps include writing proper logs, monitoring server performance, and generating clear reports to inform stakeholders.
Black Tea Testing #2 - Performance testing: why? when? how?
- 1. Performance testing Why? When? How? Serhiy Lyakhov
- 2. Why? Small start-up: To be in a trend (to launder money) ● Big start-up: To check if they could serve ● millions of customers (to launder money) ● Small company: To ensure they could become big ● Big company: To release great and fast product (not to lose customers and money) My opinion: To release normal product ●
- 3. When? ● End of the testing cycle ● Middle of the testing cycle ● Start of the testing cycle
- 4. How? Chose appropriate tool ● ● Prepare testing environment before starting testing cycle Some hints for creating and running tests. ● Write correct testing logs ● Provide understandable reports. ●
- 5. Performance testing Tool ● Support protocols ● Availability of scripting module ● Possibility of distributed testing
- 6. Testing environment ● Identify servers (app,DB) specifications ● Identify KPI for monitoring ● Install server monitoring tools
- 7. Running tests ● Define users quantity and rump-up period ● Try to cover most used User actions but not whole functionality ● Create properties file (if possible one for all tests) ● Run trial tests on testing environment
- 8. Logging ● Different logs for debugging and testing ● Better failure identification ● Disadvantage: could decrease server speed where script is running
- 9. Reporting ● Prepare good visual reports – Performance tests – Server health ● Write understandable verbal results explanation
- 10. Bad report
- 11. Good report