Testing[2] is about confirming decisions.

You want to test that the requirements are met or that a component[3] or the entire outcome[4] works as intended.

The focus for testing[2] is the whole outcome. For example,you might test that:

  • A website functions as intended for the purpose and end user requirements
  • A program performs the specified task
  • A database functions as intended for the purpose and end user requirements
  • The electronics outcome performs to specifications[1]
  • The network is functional and has no errors

As a result of the testing the student can confirm the outcome functions as intended.


Terms definitions
1. specifications. Specifications in a brief define (the nature of) the appearance and performance requirements against which an outcome can be evaluated as fit for purpose (by key and wider stakeholders). The specifications may also include constraints on both the outcome and the practice that can be undertaken to develop it.
2. Testing. Testing is about confirming decisions and ensuring that the desired result is produced form and outcome or component.
3. component. The three strands of Technology in the NZC (Technological Practice, Technological Knowledge, and Nature of Technology) – together with the six specialist knowledge and skills strands for levels 6, 7, and 8) – support the development of students’ technological literacy. Each of these strands is broken down into smaller groupings (or substrands) called “components”. For […]
4. outcome. Products and systems developed through Technological Practice for a specific purpose. A technological outcome is evaluated in terms of its fitness for purpose, and can be described by their physical and functional nature.