​

Testing

You need to plan what tests you need to carry out and the data that you will enter. You should make sure that you include valid, invalid, and boundary data in your testing. It is a good idea to record this in a test plan. Make sure that you provide evidence that you have tested every task. Be thorough and systematic. For some of the very simple tasks, you will not need a test plan but you will for more complex tasks. Fill in the results of your testing into your plan. You may not solve every problem that you encounter but it is very important to highlight potential issues. If you think about software used in environments where safety is very important, for example, medical applications, it is really important that testing is thorough and the results carefully recorded in your test log. In the real world programs are also tested with the end user.

​

Evaluations

Once you have completed the tasks, it is time to refl ect on your approach to the tasks and what your test results showed. Maybe testing indicated some flaws and you might need to correct these. It is helpful to think about what went well and maybe how you could have improved your approach and also what you learned from the exercise – planned or not! You should always refer back to the results of all of the tasks. The quality of your written communication is assessed in the testing, evaluation and conclusion section so make sure that you check that your spelling, grammar and punctuation are correct. Also, try to use correct terminology relating to the topic.

​

​

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

So for instance...using the first success criteria may look at this:

​

"My program that i created asked for a user name to be input. I created some codes that diosplayed the message on the screen successfullyu. When I got feedback back from buddy it met those requirements.

​