2. Testing is all about confidence.
Are you confident that the data provided is
reliable and accurate?

3. The Purpose of Testing
The purpose of testing is to find the errors in
your system and to correct them. This is shown
in schools as you are tested ever so often and
improved in the areas you are not so good
on, well that’s what should happen. This
improves your system to hopefully become
perfect for the user.

4. An example of testing is shown in cars. Every car
has to undergo a MOT Test, it is extremely
inconvenient if your car fails the MOT Test as it is
the same if you fail to test your database on
your course work.
:MOT sign

5. How to complete correct testing
• Draw up a test plan that will test all aspects of
your solution
• Create a testing table that will show the
outcomes of your testing
• Include screen shot evidence in the testing
table

6. What Type of testing are you doing?
There are 4 different types of testing:
1.Functional testing – each function as it is
developed using normal, erroneous or boundary
2.Navigational testing – each making sure
hyperlinks or macros work using test data (clicking on
mouse)
3.System testing – system works as a whole
4.User testing – allows the user to give feedback that
the system works appropriately to their needs.

7. What data is going to be tested?
It is very important to know what type of data
you are testing.
• There are three types of test data:
– Normal
– Erroneous
– Boundary(extreme)

8. Normal
Test that the system working under normal
conditions, is providing the correct data.
Should show that your solution accepted that
data

9. Erroneous
That the system will reject values outside of the
acceptable limits.
Should specify if the data is just outside the
boundary or is the wrong type completely.

10. Boundary
To test that the system accepts both extreme
ranges of test data
Should specify that the data is just inside the
boundary that is accepted by your solution

11. Test Data example
A field in a database is designed to accept
examination marks between 0 and 90. Validation
rules have been set up for this.
Normal Boundary Erroneous
For example: A For example: data 0 For example: data
value of 63 would or 90 should be “smith” or “92”
be fine accepted should be rejected

12. Test Plan
• Test plan needs to include tests that ensure:
– Output is 100% accurate
– Output is clear
– Data input is validated
– Printed output is as expected
– Solution meets client requirements
– Solution is user friendly

13. What should a Test Plan show?
1. Validity of data input
2. Accuracy of the output
3. Presentation of the output
4. That the solution meets the client
requirements
5. That the solution is useable by the end user
6. Incorporates the test data to be used with the
expected results

14. A Test plan Table should look like this
Test Number Purpose of Test Test Data Type Data Value Expected
Outcome

15. Example Test
Test Expected outcome
Test that all macro buttons work All macro buttons work
Text that all images are clear Logo and company name is clear
Test VLOOKUP Price per 1000 should be £32.00
Choose A4 colour 2 sides

16. Example test2
Test Expected outcome Actual Outcome Evidence
Test Total cost 318.00 318.00 Testing screen shot 1
Test validation of 1000 [extreme value] Error message only Testing screen shot 2
formulas – OK appears on erroneous
990 [erroneous test
value] - rejected

17. MUST REMEMBER
• Do make sure your screen shots are not too
small
• If you crop any screen shots, do not cut off any
part that may be useful (formula tool bar)

18. Summary
• Designing a Test strategy is necessary
• Choosing the right type of data
• Testing validation rules
• Involving other users in the testing is useful
• Documenting test results and corrective action
is necessary.