All subjects · Information Technology · WIT14 3 hour practical exam on database solutions

Testing a database solution

Edexcel IAL Information Technology · WIT14 3 hour practical exam on database solutions

Specification 19.3 asks you to test that a solution works and is fit for purpose, to test with intended users during development, and to design tests for menus, validation, and the accuracy and format of outputs.

Practise this in the app: instant marking and a fix for every mistake. Free, no email needed to start.

Practise this lesson

Functional testing and fitness for purpose

A test plan

Each test has a number, what is tested, the test data, the type (valid, boundary or invalid), the expected result and the actual result (with a screen print as evidence), plus any action taken. Here are the range-check tests, with the actual results produced by SQLite:

TestTypeExpectedActual
DailyRate = 18ValidAcceptedAccepted
DailyRate = 5BoundaryAcceptedAccepted
DailyRate = 60BoundaryAcceptedAccepted
DailyRate = 4.99Invalid (just outside)RejectedRejected
DailyRate = 60.01Invalid (just outside)RejectedRejected
DailyRate = 75InvalidRejectedRejected

Range check Between 5 And 60 on DailyRate

What to test

Worked example

Design three tests for the 'Show high value hires' query (bike-hire lines costing over 50).

  1. Test 1 (valid): a line clearly over 50, such as the Volt E2 for 3 days = 105.00: expected to appear.
  2. Test 2 (boundary): a line of exactly 50: expected not to appear, because the criterion is over 50 (> not >=).
  3. Test 3 (invalid): a line under 50, such as the Commuter for 2 days = 20.00: expected not to appear. Compare the query output with a hand calculation for each.

Answer: Valid, boundary and below-threshold tests with expected results worked out by hand.

Key idea: Test that each part works (functional) and that the whole meets user needs (fitness for purpose), involving users during development. A test plan records data, type, expected and actual results with evidence. Test menus, validation (valid, boundary, invalid), queries, calculations, output format and forms.

Check yourself

  1. In a test plan, what is the difference between expected and actual result?
    • They are always the same
    • Actual is written before testing
    • Expected is the screen print
    • Expected is decided before the test; actual is what really happened
    Show answer

    Expected is decided before the test; actual is what really happened. Comparing them shows whether the test passed.

  2. For a rule accepting ages 18 to 65, which pair is boundary test data that should be accepted?
    • 17 and 66
    • 18 and 65
    • 30 and 40
    • 0 and 100
    Show answer

    18 and 65. Boundary values on the edge that the rule includes.

  3. In the test plan for Between 5 And 60, how many of the six tests have an expected result of Rejected?
    Show answer

    3. 4.99, 60.01 and 75 are rejected.

  4. Which is the best test for a 'Preview income report' button?
    • Click it and check the income report opens in Print Preview
    • Check the button is blue
    • Count the buttons on the menu
    • Open the table in design view
    Show answer

    Click it and check the income report opens in Print Preview. Test that the action and the view are correct.

  5. Why test a solution with intended users during development?
    • It replaces all functional testing
    • It makes validation unnecessary
    • They can reveal problems with ease of use and wording that the developer misses, while changes are still easy
    • Users can fix the code themselves
    Show answer

    They can reveal problems with ease of use and wording that the developer misses, while changes are still easy. Early user feedback improves fitness for purpose.

  6. How should you test that a report's total income is accurate?
    • Calculate the total by hand from the data and compare it with the report
    • Check that the total is in bold
    • Check that the number has two decimal places
    • Print it twice
    Show answer

    Calculate the total by hand from the data and compare it with the report. Accuracy is tested against an independent calculation; formatting is a separate test.

  7. Explain the difference between testing that a database works and testing that it is fit for purpose.
    Show answer

    Testing that it works checks each function behaves correctly, while fitness for purpose checks that the whole solution meets the users' needs in their context.. Functional testing checks correctness of each part; fitness for purpose checks the solution meets the users' requirements.

Practise with instant feedback

Sources

Last updated 8 November 2026. Spotted a mistake? Tell us.