This guide presents pragmatic considerations and experienced-based best practices for performance engineers looking to automate performance testing in CI/CD pipelines.
The #1 challenge we hear from those responsible for performance testing is the difficulty in keeping up with the pace and scale of development teams so that you can deliver performance feedback early and often. They’re caught in a crossfire between performance being more imperative than ever — slow or buggy systems and applications have a material impact on customers/users, brand reputation, and bottom-line revenue — and releases coming faster than ever. The clock speed of testing is mismatched to the speed of development. With today’s automated builds taking minutes — not hours (or days) — integrating continuous performance testing into automated pipelines is the only answer.
Leave a Reply