Home Game Rules Theme Strategy FAQ












































Testing terminology

Several testing concepts have been applied in the game. The table below lists some of them and describes how to do the same in Find the Bug! Please visit ISTQB for more information.

TermTest conceptGame concept
Acceptance criteriaCriteria for component to be acceptedBugs in more than 1 component not accepted
Ad hoc testingTesting without preparationTesters assigned to test without analysis
Business criticalityA measure of impact of defectsThe severity of bugs in a bag, indicated by a colored gem (red is highest etc.)
ComponentItem that can be tested in isolationA specific module in a specific tier
Defect (bug)Flaw in component causing system failureBoth module and tier tile has a bug
Defect densityDefects in relation to component sizeNumbers/severity of bugs in component
False-failA defect is reported although no existsA detected bug that scores negatively
ModuleGroup of items tested together1 module consists of 3 tiers
Pass-failA defect is not reported although one existsA bug that is never detected
ProjectSet of tasks to undertake an objectiveThe game from start to end
Regression testTest of previously tested system after changesThe retest after fixes, when new bugs may appear
Risk-based testingTest based on impact & probability of defectsTest in modules & tiers based on gems
SeverityDegree of impact that a bug hasModule bugs have a value between -1 and 3
Technical complexityA measure of probability of defectsThe number of bugs in a bag, indicated by a colored gem (red is highest etc.)
Test automationUse of software to support test tasks, usually requires mature systemTest of entire module or tier, possible when free from bugs
Test basisDocuments on which test is based (e.g design)Bags with a number of bug/no bug tiles
Test caseSet of input and expected output1-4 squares in each component to place testers on
Test environmentHardware and software for conducting testThe game board
Test leadPerson managing test tasksThe players
Test processPlanning, analysis, design, execution, reporting and closing of testThe tasks Plan, Analyse, Test, Fix, Retest, Report and Close
TesterPerson executing test tasksThe pawns placed by the players
TierLevel of system; a 3-tier system contains presentation, application and data1 tier covers 3 modules