Testing

This Section should demonstrate the functioning of your technical solution. It should contain clear, concise and comprehensive evidence that the system as a whole operates as required.

Design of test plan

You will have mentioned the outline testing in your design. Now you should move on to showing the testing in more detail.

In table format, heading showing Reference Number, Purpose of Test, Test Data, Expected Results. Also include a column for Actual Results.  

The vast majority of your testing should be recorded as one or more videos. these can be stored as unlisted on a streaming service (youtube/vimeo etc..)  or as a shared folder on your onedrive.

The testing should be white and black box (front end testing and tests showing values changing in the code itself)

You need to show input testing with

• typical data
• erroneous data
• extreme (boundary) data

Output/process testing should include examples where you have the expected result pre-calculated and the screenshot shows the code working. Dry-Run/Hand-tracing is another possible way to show a complex algorithm working... 

Screenshots of the code running/debugging with watches is an option.

Focus especially on the parts of the code that count towards the evaluation of how complex your code is (Table A/ Table B ect...) also make sure you have shown anything that demonstrates you have met one of your objectives.