This is an automated email from the ASF dual-hosted git repository. Caideyipi pushed a commit to branch codex/it-cluster-reuse-guidelines in repository https://gitbox.apache.org/repos/asf/iotdb.git
commit 6a7028bf75c7328484d8adde7317a6f7b06215a7 Author: Caideyipi <[email protected]> AuthorDate: Thu Oct 29 10:13:31 2026 +0800 Document IT cluster reuse and test isolation --- integration-test/AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/integration-test/AGENTS.md b/integration-test/AGENTS.md index 401dbf9b779..e21be94fbfb 100644 --- a/integration-test/AGENTS.md +++ b/integration-test/AGENTS.md @@ -61,6 +61,13 @@ These instructions apply to `integration-test/` and supplement the repository-le ## Isolation and assertions +- Reuse existing test classes and fixtures, and share cluster startup and teardown across + compatible cases within a class or suite whenever possible. Avoid starting and stopping a + cluster for each test method or creating an extra cluster when an existing test cluster can + cover the scenario. Use a separate cluster or restart only when required by the tested lifecycle, + topology, configuration, or isolation. +- Keep tests that share a cluster independent of execution order: isolate their data and restore + changed state or configuration using the repository's test helpers. - Follow the neighboring tests' runner, category, and environment lifecycle conventions. Select the category matching the data model and topology required by the scenario. - Close sessions, pools, and result sets; shut down test-owned executors and clean the cluster
