Across
- 5. This debugging technique creates a 'dummy' function or subroutine which tests whether it is called or not, but is otherwise empty.
- 7. This is what all prompts or requests for input from the user should be so that the data that needs to be collected, gets collected.
- 10. This debugging technique displays messages which can tell the user what is meant to be happening e.g. "in FooBar() function" - this is used to help work out what and where problems lie.
- 12. This type of automated debugging tool stops a program at a given point but keeps everything in memory so you can check what is happening.
- 13. This debugging technique sends a Boolean (true/false) value back to indicate something has occurred to specification.
- 14. This type of error occurs when the code does not produce the desired output or otherwise does not work correctly.
Down
- 1. This type of error occurs when the program is running.
- 2. This interface design element is used to indicate empty space, usually shown in white.
- 3. This type of automated debugging tool stops programs line by line so that detailed checks of what variables and memory locations equal what value can be done.
- 4. This interface design element is important because it tells the user what is happening.
- 5. This type of error occurs when statements written code do not follow the rules of the target programming language.
- 6. This is what all error messages should be so that the user understands what is happening and possibly what can be done about it.
- 8. This interface design element is used to indicate how like or similar items are combined in the same space or location.
- 9. This type of automated debugging tool looks at given variables and how they change throughout a program.
- 11. This interface design element is used to indicate how easy it is to read text and other screen elements.