Perftiquette #10

now the 10th and probably the last episode of hashtag#perftiquette ; a short, educational and hopefully funny series on performance testing best practices.

Errors reported by your load testing tool aren’t always caused by the application – your test may be the actual culprit. Performance framework often requires significant amounts of test data to maintain, it’s a lot of configuration items and your scripts may also contain bugs, resulting in false positives.

Because of that, it’s always good to validate your test data and configuration before raising any defect. Your application may behave correctly based on the inputs you provide and your tests could simply be broken.

Save the payload of broken requests, try the same request with different data, check if the records exist in the database. These steps will save you and the developers a lot of time in attempting to replicate the issue.

Thank you for reading the Perftiquette – your engagement has been very motivational. I need to go back to work and stop browsing those memes.

hashtag#performancetesting hashtag#performanceengineering