A successful test requires more than one trouble-free demonstration. Define acceptance criteria and representative conditions before implementation.
Define scope
Describe the affected function and interfaces to other stations. Record included product variants and operating states. Unclear boundaries otherwise lead to different expectations during acceptance.
Capture comparable results
Assess agreed measures such as quality, cycle time and interruptions under documented conditions. Restart behaviour and usability may also matter. Responsible parties should define the results needed for release.
Hand over deviations clearly
Outstanding items need a description, responsible contact and due date. A partially completed test does not automatically constitute full acceptance. Documentation should distinguish tested functions from areas not yet assessed.