PXLQuill / Guide 16
Record retest outcomes
Carry remediation evidence into a clear follow-up.
01 / Return to the original finding
Use the original reproduction steps and conditions as the basis for a retest. Document any change in environment, account, build or scope that limits the comparison.
02 / Record what was observed
Use the available retest fields to capture the outcome, date and supporting evidence. Distinguish a verified fix from an issue that could not be retested.
03 / Preserve the original assessment
Keep the original finding and report as the historical record. Retest outcomes should explain what changed, not erase the original evidence.
04 / Generate the follow-up output
Use the relevant retest/report controls, inspect the resulting history and verify the selected version before delivery. Quill records your retest; it does not automatically execute the target test.
Illustrations use fictional Northstar / Atlas data. Interface availability depends on your role, the selected workspace and report state. Never use real customer data to reproduce a documentation example.