Part 10 - Testing to inform evaluation
In this part of developing a solution to a problem, you need to:
a) Provide annotated evidence for testing the solution for robustness at the end of the development process.
b) Provide annotated evidence of useability testing (user feedback).
Things to consider doing:
a) Put a heading, Robustness.
b) This section is about you or your testers trying very hard to 'break' your software. You should play the Devil's Advocate and try and do anything you can think of to make the software work in unexpected ways or to stop it working properly. This is 'robustness testing' and you may have already included some robustness tests in Part 7
c) The simpest way of doing this would be to draw up a table, list the tests you are going to do, why you are going to do that test, what data you will use if any, what you expect the outcome to be and what the result was when you carried out the test.
d) Examples of the kinds of robustness testing you could do include:
Entering in completely random strings when asked for data, including control keys and symbols.
Reading or writing to a file that doesn't exist.
Reading or writing to the cloud without an Internet connection
e) Put a heading, User feedback.
f) You should carry out the tests you said you were going to do in Part 7.