Follow one identified assembly through failed testing, controlled rework, retesting and its final disposition. Preserve the earlier failure and the work performed, while ensuring the accepted result relates to the same physical unit or batch. Dispatch should rely on the agreed release evidence, and unresolved failures should remain separate from accepted finished output.
Understand the decision
For a sample rehearsal, a board fails functional testing, receives a replacement component and then passes. Another board with a similar fault remains unresolved. The team must demonstrate that recording a successful test for one assembly does not clear the other or erase the history needed to explain the repair.
Work through the requirements
- Capture the failed test against the assembly identity.
- Record rework and any replacement material.
- Retest and approve the final disposition separately.
| Record or decision | Why it matters |
|---|---|
| Test result | Preserve outcome and assembly reference. |
| Rework record | Describe repair and consumed replacements. |
| Release decision | Identify accepted or unresolved output. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Overwriting a failed test with a passing result makes the final screen look clean but weakens the operational history. Acceptance should prove that users can explain both the current status and the sequence that produced it.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Electronics assembly in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: manufacturing product configuration ↗Odoo 19: multilevel bills of materials ↗Odoo 19: lot numbers ↗Odoo 19: quality control points ↗