feature-testing

To run end-to-end smoke tests, apply the feature-testing process to reachable targets using available fixture inputs to validate critical user journeys and multi-step service flows. This verifies that implemented features work correctly in real conditions.

Replay testing and side-effect verification is the process of checking database rows, files, and logs against the system of record to validate feature behavior. It ensures idempotency, parity, and determinism for replay-sensitive paths.

You validate feature parity and idempotency by executing replay and parity tests against reachable targets with available fixtures. This checks determinism and confirms side effects match the system of record across multi-step service flows.

Yes, feature validation requires available fixture inputs, reachable targets, and access to the relevant system-of-record for side-effect verification. Without these prerequisites, the testing cannot produce accurate pass/fail verdicts.

You generate a testing-report.md by executing smoke, replay, parity, and side-effect tests for implemented features. The report documents tested flows, execution evidence, failures, and next actions in the feature plan folder.

The best way to automate smoke testing for critical user journeys is executing real-flow tests against feature branches, API endpoints, jobs, and UI flows to validate critical paths and produce reproducible evidence for pass/fail outcomes.