Nonconformances

What is it?

A nonconformance is a short note about something noticed while executing a test case — a measurement device outside tolerance, unexpected behavior, or anything else that would otherwise go unrecorded. It has only two required fields, title and description, no status workflow of its own: it always hangs off the exact test step during which it was noticed, and is shown there as well as next to that test case in the test report. Under Quality → Nonconformances there's also an organization-wide overview of every recorded nonconformance.

How to use it

• Overview: Quality → Nonconformances lists every nonconformance in the organization with project, test case, reporter, and date, searchable and filterable by project. Clicking a row opens the affected test case.

• Record it during test execution (recommended): In the "Test case executed" dialog, choosing "Failed" shows the option "Record a nonconformance" — execution and nonconformance note are created in one step.

• Record it afterwards: On the test case detail page, the "Nonconformances" section lists notes already recorded and offers "Record nonconformance" for more — several notes on the same test case are possible.

• A failed test case without a nonconformance is flagged: On a failed test case, the "Nonconformances" section points this out as long as none has been recorded. This is the most common reason to add an observation afterwards.

• In the test report: Nonconformance notes for a test case appear in the PDF report right next to that test case.

• Deleting: If a note is wrong or no longer needed, it can be removed via the trash icon in the list.

Common issues

• "I can't delete a nonconformance." Deleting is reserved for administrators. Members with the Member role and above can record nonconformances but not delete them.
• "Who can do what?" All members can read. Recording requires the Member role or above. Deleting is reserved for administrators.
• "The execution was saved, but the nonconformance wasn't." These are two separate steps, so that a fully recorded execution never fails because of the nonconformance note. You'll get an error message in that case; add the nonconformance afterwards via the "Nonconformances" section on the test case detail page.
• "Is the nonconformance deleted when the test case disappears?" Yes — a nonconformance note has no place of its own where it would remain visible, and is removed together with the test step that triggered it.
• "Is there a status or severity filter?" No: nonconformances are plain notes without a workflow. There is currently no dedicated area for formal CAPA root-cause analysis (root cause, corrective/preventive action).