vault backup: 2026-07-02 17:14:49

This commit is contained in:
Marco van Zijl 2026-07-02 17:14:49 +02:00
parent adc7ab73c3
commit cf7d0807ab

View File

@ -1,6 +1,6 @@
ESC-P ESC-P
## Documents ## Documents
### Test requirements specification ### Test Intake / DUT Test Scope
Define targets and assumptions before design: Define targets and assumptions before design:
- DUT part number and revision - DUT part number and revision
- DUT dimensions - DUT dimensions
@ -9,12 +9,38 @@ Define targets and assumptions before design:
- Environmental requirements - Environmental requirements
- Acceptance criteria - Acceptance criteria
- Required customer inputs - Required customer inputs
### Test strategy ### Test Requirements Specification
Decide which faults are caught where and what access is required, put in a matrix: Lists all Customer Requirements, derived System Requirements, and resulting Test Requirements (what the tester must verify). Optionally Test System Requirements (what the tester must be capable of)
- Net/feature ### Test procedure specification
- Risk Describes the test flow in high-level pseudocode.
- Access method ### Test Design Specification
- Test stage? - Mechanical design
- Expected limit - Electrical design
- Electrical interface
- Instrumentation - Instrumentation
- Unresolved issues - Calibration/self-test
- Spare parts
- Supported DUT revisions
### Validation protocol + report
Defines what will be checked. The report records what happend.
For example:
- Remove testing pins to simulate 0V on power pins
- Short testing pins to simulate short-circuits or excessive load.
- Test known bad boards
### Operator instruction
Instruction for the operator on how to setup and execute the test:
- fixture photo
- DUT orientation
- barcode/serial scan step
- instruments/external tools
- start button
- pass/fail indication
- what to do on fail
- when to call test engineering
- cleaning instruction
- common failure messages
### Maintenance guide
- Daily
- On start/end of batch
- Yearly
- After 10.000 cycles