%% Last Updated: - [[2021-02-22]] - [[2021-02-13]] %% To go from being a [[Performance Tester]] to a [[Performance Engineer]], look beyond your job description and _start developing skills adjacent to testing_. ## Think about the people that you would normally rely on to run your load testing and try to learn how the skills they have. - Developers' ability to read code and diagnose why a particular transaction is failing. - An operations engineer's knowledge of cloud architecture and how to monitor server health - A solution architect's skill in putting pieces together in the most efficient way. - A business analyst's knowledge of how real users behave and why. - A front-end designer's learned aesthetic judgment and eye for usability. ## Question assumptions. When you ask a __why__ question and the answer is "Because we've always done it that way", that's how you know you've struck gold. Revisit design decisions predicated on outdated information. ## Figure out the deeper reason for your testing. Sometimes solutions are bounded by the way the problem is phrased. Challenge the problem definition and see if you can find the root problem. - [[Root problem]] ## Think about sustainability. Running a load test once isn't as good as setting up a [[CI CD Pipeline]] or framework that enables a team to run load tests regularly. [[Shift-left testing]] [[Shift-right testing]] ## Think about other forms of [[Operational testing]]|nonfunctional testing that are not being addressed.... ... such as [[Frontend performance testing]], [[Security testing]], and [[Accessibility testing]]. ![[How to Go From Performance Tester to Performance Engineer - TechBeacon#^83298539]] ## References - [[How to Go From Performance Tester to Performance Engineer - TechBeacon]]