greenrun-cli 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "greenrun-cli",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "CLI and MCP server for Greenrun - browser test management for Claude Code",
5
5
  "type": "module",
6
6
  "main": "dist/server.js",
@@ -26,8 +26,14 @@ To run tests manually:
26
26
 
27
27
  1. Use `list_projects` to find the project
28
28
  2. Call `prepare_test_batch` with the project ID (and optional filter) to get test details and run IDs
29
- 3. Execute each test's instructions using Playwright browser automation tools (`browser_navigate`, `browser_snapshot`, `browser_click`, `browser_type`)
30
- 4. Call `complete_run` with the run ID, status (passed/failed/error), and a result summary
29
+ 3. For each test, launch a **Task agent** (subagent_type: "general-purpose", model: "haiku") that:
30
+ - Reads the test instructions via `export_test_instructions`
31
+ - Executes the test using Playwright browser automation tools
32
+ - Calls `complete_run` with the run ID, status, and result summary
33
+ - Returns a one-line summary
34
+ 4. Wait for each agent to complete before launching the next
35
+
36
+ **Why Task agents?** Each test generates significant Playwright snapshot data. Running tests in Task agents keeps this data out of the parent context, preventing context bloat across a test suite.
31
37
 
32
38
  ### Auth Configuration
33
39
 
@@ -60,10 +66,15 @@ Don't ask the user for information you can derive from the codebase (base URL, l
60
66
 
61
67
  ### Creating Tests
62
68
 
63
- 1. Navigate to the page you want to test using Playwright
64
- 2. Write clear, step-by-step test instructions describing what to do and what to verify
65
- 3. Use `create_page` to register the page URL if not already registered
66
- 4. Use `create_test` with the instructions and page IDs
69
+ Use a **Task agent** per test to keep browser snapshot data out of the parent context:
70
+
71
+ 1. Use `create_page` to register the page URL if not already registered
72
+ 2. For each test, launch a Task agent (subagent_type: "general-purpose", model: "haiku") that:
73
+ - Navigates to the page using Playwright
74
+ - Explores the UI and writes clear, step-by-step test instructions
75
+ - Calls `create_test` with the instructions and page IDs
76
+ - Returns a one-line summary
77
+ 3. After each agent completes, proceed to the next test
67
78
 
68
79
  ### Bug Detection During Test Creation
69
80
 
@@ -53,7 +53,7 @@ For each **unscripted** test:
53
53
  Task tool with:
54
54
  - subagent_type: "general-purpose"
55
55
  - max_turns: 30
56
- - model: "sonnet"
56
+ - model: "haiku"
57
57
  - prompt: (see agent prompt below)
58
58
  ```
59
59
 
@@ -182,7 +182,7 @@ For each failed test:
182
182
  Task tool with:
183
183
  - subagent_type: "general-purpose"
184
184
  - max_turns: 25
185
- - model: "sonnet"
185
+ - model: "haiku"
186
186
  - prompt: (see agent prompt below)
187
187
  ```
188
188