Skip to content

Test Execution and Evidence

Execution rules

  • Record the release/build, environment, role, date/time, tester, and relevant device/browser/app build.
  • Follow the listed action while using only the approved test data.
  • Record the actual result before selecting a final status.
  • Link evidence and defects to the original test ID.
  • Retest the original case after a fix and execute affected regression tests.
  • Do not overwrite the original failure evidence.

Evidence standard

Evidence must demonstrate the relevant starting state, action, result, identifiers, and date/time where necessary.

Use the naming convention:

<TestID>_<Cycle>_<Result>_<Sequence>

Examples:

ADM-10_Cycle1_PASS_01.png
RPM-09_Cycle2_FAIL_02.mp4
E2E-04_Cycle1_PASS_Receipt.pdf

Sensitive-data control

  • Mask names, phone numbers, email addresses, identification numbers, and unrelated financial data.
  • Never capture passwords, OTPs, access tokens, private keys, or complete payment credentials.
  • Restrict evidence to approved project repositories and recipients.

Financial control

Do not repeat a payment or collection test on the same bill unless the case specifically validates retry or duplicate protection. Reconcile and label every UAT transaction.

Mobile control

For every failed mobile case, capture platform, OS version, app build, device model, permission state, network condition, and event time.