testing and documentation (debugging techniques (trace tables (trace…
testing and documentation
constructing a test plan
it is used to:
to ensure that the software is fit for purpose
to ensure that the code is efficient
to identify errors
to ensure that the code is maintainable
the test plan should follow a plan.the test data should be planned before they are implemented onto the program.
normal ,exceptional and extreme data
when the data is outside the boundaries that are set
when the data is the same as one of the boundaries that are set
when the data is in between the two boundaries that are set
trace tables are used to allow the programmer to trace the value of a variable as each line of the code is executed.the valuables are displayed in a table
Where a breakpoint is triggered at a specific point in the execution of code, a watchpoint is concerned with changes in the value of specific variables.
a dry run is when the programmer manually works through their codes to find the valuables of variables.they are found in a test plan.
When a programmer creates code they can add what is known as a breakpoint. A breakpoint is a point in the program where the code will stop executing.
syntax,logic and execution errors
a syntax error is when you incorrectly spell a word or you don't use the grammar correctly
a logic error is using an AND instead of an OR . these can be fixed by carrying out a dry run ,use a trace table or set up break points
an execution error is when the program is asked to do something it cannot do so it does something called a crash and it stops working.