1 AQA ICT AS Level © Nelson Thornes 2008 Testing a solution

2 AQA ICT AS Level © Nelson Thornes 2008 Test planning A test strategy and test plan need to be drawn up when the solution is being designed. A test strategy is an overall plan of what testing needs to be carried out without going into too much detail. A test plan goes into much more depth, giving exact details of each test to be done and what data is to be used.

3 AQA ICT AS Level © Nelson Thornes 2008 Types of test data Data for testing needs to be chosen carefully to try to prove that the solution: works with data that should work copes adequately with data that are inappropriate. Normal data is data that would be expected. It should pass validation rules and the solution should work properly, for instance the data value that is on a lookup list. Extreme data should work but is at the edges of what the solution is designed to work with. So the DVLA will accept driving licence applications from applicants aged from 17 years, but no younger. So an age of 17 would be the lowest age that was acceptable. Erroneous data should, if possible, be rejected by the solution and not cause it to fail, for example, a value that is not on the lookup list at all.

4 AQA ICT AS Level © Nelson Thornes 2008 Example Product Code BY1734 BY1963 BY5006 BY5572 BY5641 BY9007 This list is being used to look up product details via the primary key of Product Code: This value would be extreme data. These values would be normal data. A value of BZ9781 is not on the list, so it is erroneous data. If possible the system validation should stop it being entered. This value would be extreme data.

5 AQA ICT AS Level © Nelson Thornes 2008 The validity of data input The quality of information produced by any solution depends on the quality of data input. All validated fields should be tested as they are set up, but only a selection of them should be documented. The validation should allow normal and extreme data but warn the user about erroneous data whenever possible.

6 AQA ICT AS Level © Nelson Thornes 2008 The accuracy of output The accuracy of the output also depends on whether the processing has been carried out correctly. If calculations are involved, the test plan should show what data will be used for the test and what the result of the calculation should be. The result of the tests needs to be documented to prove that the calculation actually works. Other forms of processing such as queries and macros also need to be tested.

7 AQA ICT AS Level © Nelson Thornes 2008 Meeting requirements The end user needs to be involved in testing the solution to make sure it does what they wanted it to do. End users should look at: the user interface to make sure they find it easy to use. the output, making sure the correct information is included and the format is suitable for their needs. Questionnaires may often be the best way to record the opinions of ends users and audiences.

8 AQA ICT AS Level © Nelson Thornes 2008 Testing Documenting your testing (evidence) Once the test plan has been drawn up, it should be followed methodically. The results of all tests should be recorded along with evidence such as screen shots. Any corrective action that was needed should also be recorded, along with evidence that it corrected the problem. All tests should be referenced to the test plan to make it easy to follow.