Validation Evidence
Make validation reproducible by linking each sample to an expected result, finding, severity, evidence, corrective action, retest, and downstream decision.
Validation Evidence
Section titled “Validation Evidence”The Validation sheet keeps the validation plan and the resulting evidence in the same record. Each Validation ID should make it possible to reconstruct what was checked, why the sample was chosen, what result was expected, what actually happened, and what decision or corrective action followed.
Use the Documentation for the validation procedure. Use the Toolkit to preserve the project-specific sample, finding, owner, evidence, and decision trail.
Plan the check before you run it
Section titled “Plan the check before you run it”| Field group | Fields | How to use them |
|---|---|---|
| Identity | Validation ID, Activity, Data Area, Related IDs | Identify the check and connect it to the migration activity, task, risk, redirect, or decision it supports. |
| Test design | Validation Objective, Sample / Selection Basis, Record / Reference | Explain what the check proves, why the record was selected, and which source or target record is being examined. |
| Pass condition | Expected Result / Pass Condition | State an observable result that can be evaluated without guessing. |
| Responsibility and timing | Validator, Planned Date | Assign the check before the validation window begins. |
| Finding | Actual Result / Finding, Result | Record what happened and choose the appropriate result state. |
| Triage | Severity, Issue Classification, Blocking? | Describe the business significance and the most useful correction path. |
| Recovery | Corrective Action / Owner, Retest Required?, Retest Result | Make failure handling accountable and traceable. |
| Evidence and decision | Evidence Link, Decision ID, Follow-up Status, Notes | Preserve the supporting evidence and connect accepted limitations or approval decisions. |
Choose the validation activity and data area precisely
Section titled “Choose the validation activity and data area precisely”The Activity list supports Demo Migration, Full Migration, Continue the Migration with the Last Used Configuration, Continue the Migration with a New Configuration, Perform a New Migration, Launch readiness, and Post-launch monitoring.
Data areas include the supported migration categories plus Images and media, URLs and redirects, Checkout, Storefront navigation, and Target configuration. Choose the area that best describes the evidence you are evaluating. Do not use a generic area when a more specific one will make later review easier.
Use result and severity separately
Section titled “Use result and severity separately”Result records the test outcome:
- Pass;
- Pass with accepted limitations;
- Fail;
- Not applicable;
- Not tested.
Severity records the consequence of a finding: Informational, Minor, Moderate, High, or Critical.
A Fail does not become acceptable because its severity is low, and a Pass with accepted limitations is not complete until the limitation is documented and authorized where required.
Understand Follow-up Status
Section titled “Understand Follow-up Status”The workbook calculates Follow-up Status from the validation result and the evidence recorded in the row.
| Validation state | Follow-up Status behavior |
|---|---|
| Not tested | Pending |
| Fail without a corrective action/owner or evidence link | Incomplete follow-up |
| Fail with corrective action/owner and evidence | Ready for retest |
| Pass with accepted limitations without both evidence and a Decision ID | Incomplete follow-up |
| Pass with accepted limitations with evidence and a Decision ID | Decision linked |
| Pass or Not applicable | Complete |
This status is a completeness check for the record. It does not decide whether a failed result is acceptable or whether the target store can launch.
Record evidence without expanding the workbook into a data dump
Section titled “Record evidence without expanding the workbook into a data dump”A useful Evidence Link points to a secure location containing the material needed to reproduce or review the finding. Keep the Validation row focused on the identifier, expected result, observed result, decision significance, and corrective path.
Move a failed result toward closure
Section titled “Move a failed result toward closure”- Record the actual finding and choose Fail.
- Classify severity and issue type. Use the relevant Documentation troubleshooting or validation guidance to identify the safest corrective path.
- Assign the corrective action and owner. State what must change before retest.
- Mark whether retest is required. Do not change the original finding to hide the first failure.
- Add the evidence link. Preserve enough evidence for review or support escalation.
- Retest the affected condition. Record the retest result and connect any required acceptance decision.
Connect validation to the relevant procedure
Section titled “Connect validation to the relevant procedure”Use the appropriate Documentation page to determine the sample, checks, and pass conditions. Common starting points include:
- Review Demo Results;
- Validate Full Migration Results;
- Validate Content, URLs, and Redirects;
- Define Sign-off Criteria.
Next Steps
Section titled “Next Steps”When a validation result affects URL continuity, maintain the URL-level evidence in Redirects. When a result requires authorization or an accepted limitation, record the decision in Decisions and sign-off.