Acceptance and test plans: every test step with result, finding and evidence

The test plan as a template

Test steps are created with instructions, expected duration and a responsible person; dependencies become predecessors. Every test run is its own live plan from the template – repeats after a fix run through the same proven sequence.

• Factory acceptance (FAT) and site acceptance (SAT) for machines and plants
• Software tests: integration, regression and user acceptance tests (UAT)
• Validation runs in regulated environments, such as installation, operational and performance qualification
• Test instructions in Markdown, measurement records and screenshots attached to the step

Result and finding directly on the step

Whoever tests reports the step back and records the result as a finding – with measured values, deviations and attachments. Forcing a step despite an open prerequisite is only possible with a reason, and that reason is part of the history as well.

For regulated industries

Medical devices, pharma, laboratories and aviation require traceable procedures. CaRD Plan records every step with person, time and comment and delivers the sequence as a building block of your documentation. It does not do the validation for your intended use – it delivers the evidence you need for it.

The protocol writes itself

At the end there is a closing report as PDF with all steps, times, findings and deviations – plus the project archive with attachments and the complete history. No collecting afterwards from e-mails and spreadsheets.