# Baseline review rules

Use this file only when the canonical workspace document `../docs/refs/TiDB Cloud E2E case review rules.md` is unavailable. The canonical document remains the source of truth.

- **Order — P1/P2:** Keep steps in intended low-to-high lifecycle order. Investigate duplicate or decreasing values and confirm dependencies around inserted decimal orders.
- **API path — P1:** Avoid environment-specific absolute URLs. Relative request URLs are assembled from host, `scenario.context.base_path`, and `request.path`.
- **Expectations — P1/P2:** Assert the correct status and meaningful response state or fields. Do not accept a success code while omitting behavior essential to the scenario.
- **Retry — P2:** Give polling steps a bounded, justified retry window. Review any total wait over 30 minutes. For intentional wait steps implemented through a failing expectation, require `continue_on_unexpected: true`.
- **Sensitive information — P0:** Never commit cloud access keys, secrets, tokens, passwords, DSNs, or equivalent credentials. Bind values from workflow secrets or runner placeholders.
- **Resource naming — P3:** Name created resources after the tested scenario or feature. Reject generic names such as `cluster1` or `test-cluster2`.
- **Resource preparation — P2:** Use the smallest practical test resource specification unless the scenario explicitly tests size or capacity.

Reference findings to `../docs/refs/TiDB Cloud E2E case review rules.md` when that file exists.