•  Constructing a Test Plan: A set of test data which has been created to systematically and comprehensively to test the software; makes use of the following test data
  • normal – ensures the program works when used normally
  • extreme – ensures the program works when data is used that is on the boundaries of what is considered normal
  • exceptional – ensures a program can handle situations that it has not been designed to cope with; out with the boundaries
• Comprehensive Testing: when every aspect of the software is tested
• Syntax Error: a misspelling of a keyword or mistake in the structure of a program such as missing an ‘end if’
• Logic Error: program will run but not as the programmer intended it to; for example when calculating the average it should be (a+b)/2 instead of a+b/2
• Execution Error: an error occurs when the program is run, causing it to crash
• Dry Runs: manual run through of pseudocode or source code of program, taking notes of the values of variables at various points in the process
• Trace Tables: similar to the table used during a dry run but is often used to test an algorithm for a specific sub program
• Breakpoints: a set point in a program where it will stop execution so that the values of variables can be examined

Thank you to C O’Toole & A Madill from Braidhurst High School for allowing me to edit and publish this here.