From 9232f9b04cd617ba10c582fa4dea4e66dcfd621f Mon Sep 17 00:00:00 2001
From: Anh Tran <124683165+anhtnt90dev@users.noreply.github.com>
Date: Tue, 9 Jun 2026 00:36:10 +0700
Subject: [PATCH] docs: clarify local plugin test commands

---
 docs/testing.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/docs/testing.md b/docs/testing.md
index 414d69790c..a4bab33a7a 100644
--- a/docs/testing.md
+++ b/docs/testing.md
@@ -21,6 +21,33 @@ Live in `tests/`. Currently:
 
 Run plugin tests via the relevant directory's `run-*.sh` or `npm test`.
 
+Fast local checks:
+
+```bash
+# Brainstorm server JS tests. Install the test-only ws dependency first.
+cd tests/brainstorm-server
+npm ci
+npm test
+
+# Shell lint wrapper tests. These use stubbed shellcheck/shfmt binaries.
+cd ../..
+bash tests/shell-lint/test-lint-shell.sh
+```
+
+The Windows brainstorm lifecycle test intentionally waits past the 60-second
+owner-process check twice. Give it at least 3 minutes:
+
+```bash
+bash tests/brainstorm-server/windows-lifecycle.test.sh
+```
+
+On Windows, run the shell tests from Git Bash or invoke Git Bash explicitly
+from PowerShell, for example:
+
+```powershell
+& 'C:\Program Files\Git\bin\bash.exe' tests/brainstorm-server/windows-lifecycle.test.sh
+```
+
 ## Skill behavior evals
 
 Live in `evals/`. Drill is the harness; scenarios live at `evals/scenarios/*.yaml`. See `evals/README.md` for setup. Quick start: