Section 3: Trialling and Testing

Trialling and testing are fundamental processes used throughout digital development to ensure your outcome is fully functional, usable, and robust before deployment.

Merit Focus

Effectively test and trial components (using systematic test plans and user trialling) to detect bugs and make necessary improvements.

Excellence Focus

Synthesise trialling results to refine your outcome iteratively, justifying how rigorous testing resulted in a high-quality, fit-for-purpose solution.

1. Core Reading & Testing Frameworks

A. Functional Testing vs. User Trialling

Functional Testing: Checks whether code, links, forms, and database queries work according to technical specifications (e.g., verifying that empty input fields throw validation errors).

User Trialling: Involves real end-users interacting with your interface to evaluate usability, layout logic, readability, and overall user experience (UX).

B. Types of Test Data

When running systematic tests on inputs, forms, or functions, you must use three distinct types of test data:

Expected / Normal Data: Data within standard operational parameters (e.g., entering "John" in a name field). Should pass cleanly.
Boundary / Edge Data: Data at the extreme limits of acceptable ranges (e.g., entering a 100-character name if 100 is the limit).
Invalid / Erroneous Data: Data that violates formatting or constraints (e.g., entering letters into a phone number field). Must trigger helpful validation error messages without crashing.

C. Iterative Improvement & Documentation

Testing is not a one-off final step. It is an iterative cycle: Test → Identify Issue → Refine Code/Design → Retest. Documenting both "Before" and "After" states is crucial to demonstrating an advanced development process for NCEA assessment.

2. Practical Task: Construct a Systematic Test Plan

Practice logging component tests. Your test cases auto-save so you can return to review them at any time:

Component / Element

Test Data Type

Test Input Used

Expected Result

Outcome / Action

Component	Type	Input Used	Expected Result	Status	Action

3. Knowledge Check Quiz

Verify your understanding of trialling and testing principles:

Score: 0 / 0

4. Excellence Reflection Practice

For Excellence, you must justify how testing feedback directly influenced design refinements. Your written work auto-saves continuously.

Scenario: During user trialling, 4 out of 5 end-users struggled to find the contact form because it was hidden in a secondary footer menu. Explain how you would address this feedback, retest the solution, and document the improvement.