testing and documentation (test plan (to identify errors, to ensure that…
testing and documentation
to identify errors
to ensure that software is fit for purpose
to ensure that code is efficient
to ensure that code is maintainable
Syntax, execution and logic errors
This is an error in the spelling or grammar used when coding.
Sometimes called a runtime error, execution errors only become evident during run time
An execution error occurs when a program is asked to do something that it cannot, resulting in a ‘crash’
An error in the logic of the code such as using ˂ instead of ˃ or AND instead of OR
dry runs, trace tables, breakpoints and watchpoints
A dry run is the process of a programmer manually working through their code to trace the value of variables. There is no software involved in this process.
Trace tables are used to find errors the value of variables are displayed in a table to make it easier to find errors
A breakpoint is a point in the program where the code will stop executing.
watchpoints are breakpoints for variables instead on a line a watchpoint is attached to a variable
programmers will make use of comments to make it easier to change the program at a later date
programmers will have a test history to see what the have done, it will include the original test plan and any test data achieved from the plan
fitness for purpose
a program will be evaluated to see if it does what was required of it at the start
is the program easy to read and easy to follow
a program is robust is it doesn't crash or break down even if the wrong data type is inputted