Map the failure risk to the check
| Possible failure | Check to define | Record to retain |
|---|---|---|
| Wrong pinout or connector orientation | Compare wire/connector identity and connections with the controlled drawing before energizing | Drawing revision, connection result and disposition |
| Open or unintended connection | Defined continuity and short-circuit checks with an appropriate fixture | Test limit, fixture revision and failed connections |
| Incomplete seating or unsupported cable | Inspect engagement, locking, strain relief and routing against the assembly definition | Inspection finding and approved correction |
| Intermittent product behavior | Exercise defined interfaces and operating conditions with the installed harness | Stimulus, configuration, measured result and failure timing |
| Wrong cable variant or label | Reconcile item identity and product variant with the system BOM and build instruction | Unit/batch identity and installed variant |
| Failure after rework | Repeat the affected checks under the released procedure | Original failure, approved action and retest result |
The table is a planning framework. Pull, electrical-safety or environmental tests need their own specified loads, methods, equipment and acceptance criteria; the guide does not establish universal test limits.
Release the interface before preparing the fixture
Reconcile the pinout, connector references, wire requirements, power connections and variant differences. Confirm the safe energizing sequence and the test access that remains after installation. An unresolved connection should remain an open engineering item rather than an operator assumption.
Define whether the fixture checks a standalone harness, the board-harness combination or the enclosed product. In a box build work package, installed routing, mechanical fit and system interfaces also need an agreed inspection or verification step.
Define what the test can demonstrate
A continuity result verifies the specified electrical paths under that method. It does not by itself demonstrate connector retention, performance under load or every system function. A functional result covers the functions and conditions actually exercised. Discuss inspection and test coverage before assuming that a test name guarantees complete coverage.
Keep failure analysis useful
Where the agreed traceability level permits, associate results with the product revision, harness variant, firmware/configuration and fixture or procedure revision. Record whether the finding is at the board, harness, connector, installation or configuration level. Retain failed results and approved repair/retest history according to the quality record requirements.
Illustrative pilot review
If a board passes its standalone test but fails after the harness is installed, compare the released connection definition, actual assembly and system-test conditions before assigning the failure to the board. Document the observation, the proposed correction and the checks that must be repeated. This is a diagnostic example, not a reported Keep Best project result.
Prepare the quotation and review
Add the harness drawings, system interfaces, existing test assets and acceptance requirements to the box build RFQ package. For connected-device variants, the IoT final-test checklist adds configuration and connectivity questions. Share the integration requirements with the available files and missing-item owners.