“Not testing performance early in development and not testing it later in production. Today’s tools make it easier to “shift-left” moving performance testing into the development cycle so that all new code can have not only unit, smoke, and functional tests, but also performance tests that will detect performance regressions and defects before the code becomes part of the project. Allowing code that performs poorly into a project increases the cost to address this defect later. Adding performance testing as a ‘shift-right’ into production ensures that the production system truly can scale and perform well when demand is higher than a development or pre-prod test would simulate. Testing in production also allows testing third-party components as a part of an integrated performance load test. You don’t want a third-party feature to be the blocking item that can’t perform at scale.” – Tom Chavez | Sr. Evangelist, SOASTA
About the Author
Amy is the Marketing Manager at SOASTA, where she specializes in content marketing, growth-hacking, wordsmithing, and go to market strategies. She is fascinated with the correlation between web performance, neuroscience, and how this translates into success for modern digital businesses.