- This is the first installment of a currently unknown number of posts about heuristics and mnemonics I find valuable when teaching and conducting performance testing.
- Other posts about performance testing heuristics and mnemonics are:
- Installment 2 - Classify Performance Tests: IVECTRAS
- Installment 3 - Model Workloads for Performance Testing: FIBLOTS
- There is not a "one-size-fits-most" approach to performance testing, but I have become rather convinced that there are nine principles that are (almost always) applied (or at least actively considered) in successful performance testing projects. I remember those principles by remembering:
- CCD IS EARI
- Context: Project context is central to successful performance testing.
- Criteria: Business, project, system, & user success criteria.
- Design: Identify system usage, and key metrics; plan and design tests.
- Install: Install and prepare environment, tools, & resource monitors.
- Script: Implement test design using tools.
- Execute: Run and monitor tests. Validate tests, test data, and results.
- Analyze: Analyze the data individually and as a cross-functional team.
- Report: Consolidate and share results, customized by audience.
- Iterate: "Lather, rinse, repeat" as necessary.
- For more see Developing an approach to performance testing -- CCD IS EARI.
Chief Technologist, PerfTestPlus, Inc.
Co-Author, Performance Testing Guidance for Web Applications
Author, Web Load Testing for Dummies
Contributing Author, Beautiful Testing, and How To Reduce the Cost of Testing
"If you can see it in your mind...
you will find it in your life."