Expected decision
Label each sample with the agreed accept, reject or review decision and the reason. Define borderline cases with the quality team rather than changing the limit after observing the result.

Plan adhesive bead inspection challenge tests for gaps, offset, excess material, marginal samples, recipe changes and missing or uncertain results.
Agree expected decisions before testing adhesive bead inspection. Use accepted, clearly rejected and marginal samples to challenge continuity, width and path position separately; retain the observations and the actual line response.
Challenge missing images, wrong recipes and uncertain results as well as visible defects. The examples below are proposed test cases, not reported performance results.
A rejected sample is useful only if the result belongs to the right physical part and the agreed response occurs. Record the sample, part variant, recipe, production condition, decision and any unresolved case.
Discuss your application

Label each sample with the agreed accept, reject or review decision and the reason. Define borderline cases with the quality team rather than changing the limit after observing the result.
Include normal appearance variation, marginal beads, realistic presentation and intended timing. Repeat relevant challenges after recipe changes and recovery from a stop.
Keep the result record and confirm the required hold or reject response. Agree repetitions, acceptable outcomes, responsibilities and unresolved actions before acceptance.
Include a break on the required bead path, including a difficult corner or join. Record whether the complete required path is assessed.
Challenge an agreed narrow/wide example and an offset example separately. Passing a width check must not automatically count as passing the path-position check.
Include the visible tails, extra material or double-dispense condition relevant to the part. Agree where this material matters and how it is judged.
Include examples near the agreed decision boundary and normal appearance variation. Retain uncertain cases for review instead of silently relabelling them.
Check the agreed response to an incorrect recipe, missed trigger or unusable image. Confirm which part each result belongs to.
Check the physical hold/reject response and recovery under the agreed line conditions. Document the result, exceptions and actions needed before handover.