Functional verification

Functional testing with the limits left visible.

A unit that powers on has passed one observation. A useful assessment records the checks that matter for the item category, what happened during those checks and what could not be verified.

Testing approach

Test what is appropriate — and say exactly what was tested.

Functional testing is configured by category and assignment. It can include power state, controls, displays, cycles, outputs, ports, connectivity or other observable functions when access, utilities and safety conditions permit.

The resulting record does not collapse “powered on,” “partially tested” and “fully checked to the agreed procedure” into the same status. Each result carries its procedure and limitations.

A traceable test record includes

  • Unit identity and starting condition
  • Test procedure or checklist used
  • Utilities, accessories and inputs available
  • Observable results and fault behaviour
  • Photo or video references where relevant
  • Checks not completed and the reason

When a unit is not energized

Unsafe conditions, contamination, missing connections, physical damage or client instructions may make energization inappropriate. The report should record that decision rather than treating “not tested” as “failed.”

Prepare an assignment

Prepare the assignment brief.

Use the intake worksheet to record the item types, quantity, location and required decision. This pre-launch form does not transmit information.

Prepare an assignment brief