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.
Functional testing and fitness for purpose
- Functional testing checks that each part works: validation accepts and rejects the right data, buttons do what their labels say, queries return the right records, reports calculate correctly.
- Fitness for purpose asks whether the solution meets the users' requirements in their context: can the counter assistant actually book a hire quickly?
- User testing during development: intended users try tasks and give feedback (ease of use, wording, speed), and the design is improved before it is finished.
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:
| Test | Type | Expected | Actual |
|---|---|---|---|
| DailyRate = 18 | Valid | Accepted | Accepted |
| DailyRate = 5 | Boundary | Accepted | Accepted |
| DailyRate = 60 | Boundary | Accepted | Accepted |
| DailyRate = 4.99 | Invalid (just outside) | Rejected | Rejected |
| DailyRate = 60.01 | Invalid (just outside) | Rejected | Rejected |
| DailyRate = 75 | Invalid | Rejected | Rejected |
Range check Between 5 And 60 on DailyRate
What to test
- Menus and buttons: every button opens the correct object in the correct view (for example a report in Print Preview), and Exit closes the database.
- Validation: each rule with valid, boundary and invalid data; error messages appear and make sense.
- Queries: compare results with a manual check of the data. For a criterion such as >=1000, include records at 1000 and just below.
- Calculations: work one result out by hand (rate x days) and compare.
- Output format: titles, currency formatting, grouping, totals, no truncated labels, page layout in Print Preview.
- Forms: new records save, defaults appear, locked fields cannot be edited, cancellation works.
Worked example
Design three tests for the 'Show high value hires' query (bike-hire lines costing over 50).
- Test 1 (valid): a line clearly over 50, such as the Volt E2 for 3 days = 105.00: expected to appear.
- Test 2 (boundary): a line of exactly 50: expected not to appear, because the criterion is over 50 (> not >=).
- 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.
Check yourself
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Sources
- Pearson Edexcel International Advanced Level in Information Technology specification (Issue 2, February 2021): Unit 4, Topics 17 to 19
- Pearson: WIT14/01 examiner report, June 2025
- Pearson: IAL Information Technology scheme of work for Unit 4
Last updated 8 November 2026. Spotted a mistake? Tell us.