# Staging Test Setup And Reset Runbook

## Before A Test Cycle

1. Confirm deployed branch/commit.
2. Confirm staging `.env` uses production-like settings with no real customer data.
3. Confirm database backup/snapshot.
4. Confirm seed/demo data set is present.
5. Confirm Stripe test mode only.
6. Confirm media scanning/GD readiness if uploads are in scope.
7. Fill `Tester Quick Start` with staging URL, accounts, demo events, and evidence folder.

## Reset Between Cycles

- Do not use destructive reset on production-like data without architect approval.
- Clear or archive test orders only if the architect confirms accounting impact.
- Release stale seat holds using the documented scheduler/command.
- Remove test uploads if retention/media scan tests require a clean state.
- Recreate required demo events listed in `Test Data Setup`.
- Record reset time, owner, and any data intentionally preserved.

## Repeatability Requirements

- Every tester must know which event/venue/seat map to use.
- Payment tests must use Stripe test mode.
- Failed/blocked tests must be reproducible after reset.
- Test data names should include a date/time suffix where practical.