Factory and Site Acceptance Testing for Custom Electronics and IoT Systems

Link every test to a requirement

Assign requirement IDs and write the setup, steps, expected result and pass criterion. Identify who performs and witnesses each test. Replace vague claims such as fast or reliable with measurable conditions agreed for the project. List exclusions and dependencies so missing site equipment is not confused with a passed test.

Use FAT to expose integration problems

Check I/O mapping, scaling, timestamps, configuration, alarms and user roles with representative devices or documented simulators. Include startup, sensor disconnection, storage limits and network interruption. For firmware updates, test interruption and recovery. Record limitations of simulation so they become explicit site-test items rather than hidden assumptions.

Use SAT to verify the installation

Confirm actual sensor placement, communications, power recovery and integration with site equipment. Check that recipients receive the intended alerts and users can perform assigned tasks. Coordinate tests with operations and use safe simulation where creating a real fault is inappropriate. Verify documentation matches the installed configuration and version.

Close defects and hand over evidence

Record failed cases, owners, corrective actions and retest results. Distinguish acceptance with agreed outstanding items from unconditional completion. Deliver configuration backups, version records, test reports and operating instructions. Agree support contacts and warranty boundaries in the project documentation; an acceptance test is not a substitute for every applicable certification or compliance assessment.

FAQ