|
Variable Analysis
|
Identify anything whose value can change. Variables can be obvious, subtle, or hidden.
|
|
TouchPoints
|
Identify any public or private interface that provides visibility or control. Provides places to provoke, monitor, and verify the system.
|
|
Boundaries
|
Approaching the Boundary (almost too big, almost too small), At the Boundary
|
|
Goldilocks
|
Too Big, Too Small, Just Right
|
|
CRUD
|
Create, Read, Update, Delete
|
|
Follow the Data
|
Perform a sequence of actions involving data, verifying the data integrity at each step. (Example: Enter → Search → Report → Export → Import → Update → View)
|
|
Configurations
|
Varying the variables related to configuration (Screen Resolution; Network Speed, Latency, Signal Strength; Memory; Disk Availability; Count heuristic applied to any peripheral such as 0, 1, Many Monitors, Mice, or Printers)
|
|
Interruptions
|
Log Off, Shut Down, Reboot, Kill Process, Disconnect, Hibernate, Timeout, Cancel
|
|
Starvation
|
CPU, Memory, Network, or Disk at maximum capacity
|
|
Position
|
Beginning, Middle, End (Edit at the beginning of the line, middle of the line, end of the line)
|
|
Selection
|
Some, None, All (Some permissions, No permissions, All permissions)
|
|
Count
|
0, 1, Many (0 transactions, 1 transactions, Many simultaneous transactions)
|
|
Multi-User
|
Simultaneous create, update, delete from two accounts or same account logged in twice.
|
|
Flood
|
Multiple simultaneous transactions or requests flooding the queue e.g. making/selecting a submit request/button multiple times
|
|
Dependencies
|
Identify “has a” relationships (a Customer has an Invoice; an Invoice has multiple Line Items). Apply CRUD, Count, Position, and/or Selection heuristics (Customer has 0, 1, many Invoices; Invoice has 0, 1, many Line Items; Delete last Line Item then Read; Update first Line Item; Some, None, All Line Items are taxable; Delete Customer with 0, 1, Many Invoices)
|
|
Constraints
|
Violate constraints (leave required fields blank, enter invalid combinations in dependent fields, enter duplicate IDs or names). Apply with the Input Method heuristic.
|
|
Input Method
|
Typing, Copy/Paste, Import, Drag/Drop, Various Interfaces (GUI v. API)
|
|
Sequences
|
Vary Order of Operations Undo/Redo Reverse Combine Invert Simultaneous
|
|
Sorting
|
Alpha v. Numeric Across Multiple Pages
|
|
State Analysis
|
Identify states and events/transitions, then represent them in a picture or table. Works with the Sequences and Interruption heuristics.
|
|
Map Making
|
Identify a “base” or “home” state. Pick a direction and take one step. Return to base. Repeat.
|
|
Users & Scenarios
|
Use Cases, Soap Operas, Personae, Extreme Personalities
|
|
RCRCRC
(Karen N. Johnson)
|
Recent - what testing around new areas of code should I think about?
Core - what essential functions or features must continue to work?
Risky - what features or areas of code are inherently more risky?
Configuration Sensitive - what code is dependent on environment settings?
Repaired - what code has changed to address defects and potentially created issues?
Chronic - what code typically breaks features that need to be tested?
|
|
FAILURE
(Ben Simo)
|
Functional, Appropriate, Impact, Log, UI, Recovery, Emotions
|
|
WWWWWHKE
(sounds like “wiki” (Darren McMillan)
|
Who is this for? What is this for? When & by whom is it to be done? Where is it being done? Why is it being done? How is it being achieved? What questions does my Knowledge & Experience produce?
|
|
Diversity & Inclusion
(Callum Akehurst-Ryan)
Combat Bias with Heuristics of Diversity
(Ash Coleman)
|
Does this work for me? Does this work for them? Does this work for someone I have never considered or ever met?
|
|
Seven Dwarfs
(Cassandra H. Leung)
|
Grumpy, Happy, Sleepy, Bashful, Sneezy, Dopey, and Doc.
|
|
Specs/Designs Watchlist
(Gerard McCann)
|
Ambiguity, weasel words (like could, should or may), Fudge (e.g. statements like ‘this will be resolved at a later date’, but no specifics around who and when), Confusing terminology, jargon or obscure acronyms, Oversimplification, Overcomplication
|
|
TORCH
(Simon Tomes)
|
Timer, Oracles, Risks, Consider these questions, Heuristics
|
|
MCOASTER
(Michael Kelly)
|
Mission, Coverage, Obstacles, Audience, Status, Techniques
Environment, Risk
|
|
Seen and Heard
(Ady Stokes)
|
For everything you can see, is it announced by a screen reader? For everything you hear, can it be read (transcript, subtitles, captions, audio descriptions)
|
|
TuTTu and TaTTa
(Mark Winteringham)
|
Testing the UI or Testing Through the UI
Testing the API or Testing Through the API
|
|
SACRED
(Richard Bradshaw)
|
State Management, Actions, Codified Oracle, Reporting, Execution, Deterministic
|
|
TRIMS
(Richard Bradshaw)
|
Targeted, Reliable, Informative, Maintainable, Speedy
|
