Performance Test Strategy

The elements of a solid performance test strategy, including entry and exit criteria.

By SixQuality · Performance Testing

A performance test is only as good as the strategy behind it. A clear strategy defines what you will test, how, in what environment, and — crucially — the criteria that decide when to start, pause, resume, and stop. Here are the elements that belong in it.

Core elements of the strategy

Entry, suspension, resumption, and exit criteria

Well-defined criteria keep a performance test disciplined:

CriterionMeaning
EntryConditions that must be met before testing starts (stable build, ready environment, approved scripts and data).
SuspensionConditions under which testing is paused (environment failure, blocking defect, invalid results).
ResumptionConditions required to restart after a suspension (issue resolved, environment restored).
ExitConditions that define "done" (targets met or clearly not met, agreed scenarios completed, results analysed).

Strategy to execution

Plan + environment
→
Script + data
→
Run via load injectors
→
Analyse + report
Correlation matters: real applications pass dynamic values (session ids, tokens) between requests. Scripts must capture and reuse these — a technique called correlation — or the test will not behave like a real user.

Conclusion

A strong performance test strategy covers the plan, environment, schedule, scripting, data, load injectors, and reporting — all governed by clear entry, suspension, resumption, and exit criteria. Get the strategy right and the numbers you produce will be trustworthy.

Next: Types of Performance Test →

← Back to all articles