Spike Testing
Spike testing is a type of performance testing that evaluates how a system behaves when subjected to sudden, extreme increases or decreases in workload.
“Testing to determine the ability of a system to recover from sudden bursts of peak loads and return to a steady state.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Spike Testing?
The objective is to determine whether the system can handle abrupt traffic changes and recover successfully afterward.
Sudden workload changes: Simulates unexpected traffic spikes.
Recovery evaluation: Verifies system stability after the spike.
Performance focus: Identifies bottlenecks under rapid load changes.
Real World Example
A regulated product team is preparing a release where Spike testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Spike testing as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Spike testing and similar ideas.
The page becomes useful in practice because Spike testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Spike testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Spike testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Spike Testing. Test your understanding with topic-specific questions in our Mock Exams.