Rstest debugging

Diagnose the measured lifecycle stage before changing configuration. Keep behavior and the test manifest fixed, change one variable at a time, and remove experiments that do not produce a repeatable benefit.

Workflow

1. Establish comparable single-file and full-scope baselines with references/performance-measurement.md.
2. Run rstest --trace when supported and classify the cost as host build/startup, runtime load/setup/collect, test bodies/hooks, or CLI/report/teardown overhead.
3. Use DEBUG=rstest for resolved config and build output. For Rstest 0.11.7+ experimental per-test bundle coverage, follow references/performance-measurement.md. Use Rsdoctor only after evidence points to the compiler. Use verbose reporting or a profiler only after narrowing to runtime files/cases.
4. If dependency loading or compilation is implicated, read references/dependency-bundling.md. Compare the environment default, bundleDependencies: false, and bundleDependencies: true; neither bundling nor externalization is universally faster.
5. If a fully mocked heavy module still reaches the build graph, read references/mocked-module-build-graph.md before testing an exact external.
6. If assets, console output, pools, isolation, or memory dominate, read references/runtime-output-memory.md.
7. Rerun the representative file and full scope. Keep a change only when behavior, discovery, snapshots, and coverage remain valid and the benefit survives repeated measurement. Remove traces, profiles, and .rstest debug artifacts created by the diagnosis before handing off.

Guardrails