Skip to content

armgit / zulip

Public Imported from GitHub
0

Zulip server and web application. Open-source team chat that helps teams stay productive and focused.

claude: Consolidate the two "which tests to run" sections.

Evy Kassirer671a9dada214
diff --git a/AGENTS.md b/AGENTS.md
index 859c0cb3a28..e0a0c35e0ac 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -112,14 +112,8 @@ commit from other changes.
### 4. Verify Before Finalizing
-Run tests before making a commit. Always manage your time by running
-specific test collections, not the entire test suite:
-
-```bash
-# Includes mypy and typescript checkers
-./tools/lint path/to/changed/files.py
-./tools/test-backend zerver.tests.test_relevant_module
-```
+Run the linter and the relevant tests before making each commit; see
+"Testing Requirements" below for instructions.
Run through the `/self-review` skill's checklist before suggesting opening
a PR (`.claude/skills/self-review/SKILL.md`).
@@ -202,12 +196,14 @@ When writing tests, follow our testing philosophy in
`.claude/rules/testing.md` (loaded automatically when you work on
test files).
-### Before Submitting:
+Manage your time by running specific backend test collections, not
+the entire suite; the node suite is fast enough to run in full.
```bash
-./tools/test-js-with-node # JavaScript tests; full suite fast enough
-./tools/lint # Run all linters
-./tools/test-backend # Python tests
+# Includes mypy and typescript checkers
+./tools/lint path/to/changed/files.py
+./tools/test-backend zerver.tests.test_relevant_module
+./tools/test-js-with-node
```
### Manual Testing for UI Changes