Answer:
1 developing a set of test criteria
2 applying 'non-operating' tests to ensure that equipment can stand up to expected levels of physical handling, such as transit drop tests
3 examining if appropriate any code 'hard wired' in hardware (this code is sometimes known as firmware) to ensure its logical correctness and to ensure that appropriate standards are followed
4 applying functional tests to determine whether the test criteria have been met
5 applying qualitative assessments to determine whether the test criteria have been met
6 conducting tests in both 'laboratory' conditions and in a variety of 'real life' conditions
7 conducting tests over an extended period of time, to ensure systems can perform consistantly
8 conducting 'load tests', simulating as closely as possible a variety of 'real life' conditions and using or exceeding the amounts of data that could be expected in an actual situation
9 verifying that 'what goes in' is 'what comes out', by entering known data and checking that the output agrees with the input
Explanation:
