Menu

Testing - Match-up

Match-up definitions and answers with key terms and examples. Press submit to check your answers.

Iterative testing
Final testing
Syntax error
Logic error
Normal test data
Boundary test data
Invalid test data
Erroneous test data
Test plan
Refining algorithms
Expected result
Actual result


Answers
A mistake that allows a program to run but causes it to produce unexpected or incorrect output.
Checking the completed program at the end of production to ensure all parts work together and meet requirements.
A schedule of checks giving the purpose, data, type of data, expected result and actual result of each.
A mistake that breaks the grammatical rules of a programming language, stopping it from being translated or run.
Data of the correct type but with a value outside the accepted range, which the program should reject.
Data that is typical and sensible, which the program should accept without causing any errors.
The outcome produced when a test is run, recorded to show whether the test passed.
Data of the correct type on the very edge of validity, such as the highest and lowest acceptable values.
The outcome that a test should produce if the program is working correctly.
Fixing an error found during a test and then rerunning the same test to check the fix.
Data of the incorrect type, such as text where a number is expected, which the program should reject.
Checking each part of a program as it is written, with errors fixed and the part retested during development.
Log in or sign-up to access the match-up activity



Don't have a login?

You can still revise this topic