Transcript
Automation is a method, not automatic evidence
Automated testing can be excellent validation evidence for stable, repeatable behavior. First define the G X P function, requirement, failure scenario, expected result, environment, data, and execution record. A green pipeline alone does not explain what was tested or whether the test could detect the important failure.
Show that the test is suitable
Control the test tool, code, libraries, selectors, data, access, and environment. Derive expected results from the approved requirement, not from the same application behavior. Deliberately introduce or simulate a relevant failure and confirm that the automation fails with a useful record.
Review failures and control change
Investigate a failed execution before rerunning. Retain inputs, outputs, logs, version, result, reviewer, deviation, and traceability. Assess changes to the application, test code, tool, dependency, data, and acceptance criteria. Automation supports validation when its own intended use and controls are demonstrated.