Embedded Files
Developmental Testing - 5 marks
Developmental Testing - 5 marks
What does it need to contain?
What does it need to contain?
Take note of the highlighted KEY words
A Bit of Background:
A Bit of Background:
What is Developmental Testing?
Developmental Testing is like a ‘log’ of testing carried out during Prototype Development.
You will show screenshots of problems that occurred, and describe what you did to resolve them.
This section should include errors found when developing your prototype, plus any further errors found during the development of your final solution.
This section is explicitly to show errors and their resolution during development. You do not need a test plan in this section.
How does it differ from the Testing Section (later on in the Project) ?
The Testing Section has a Test Plan, which lists all the tests you want to show evidence of (using screenshots & annotation).
The Testing Section shows your system’s functionality works correctly (i.e. no errors) and the evidence needed in the Testing Section is screenshot AFTER all coding is complete.
Developmental Testing Log
Developmental Testing Log
Purpose - To document all errors found during both prototype development and final system development. This log must be kept up to date throughout your coding, as you find errors.
For every coding error you encounter:
Screenshot your error
Describe what you are going to do to put it right (the mark scheme says you have to 'fully justify' your changes)
Screenshot your code working after the changes have been made
Annotate all screenshots to explain what you are evidencing
You must show a selection of all errors found (not the same types of errors over and over again).
Page updated
Report abuse