@sun-asterisk/sungen 3.2.21-beta.3 → 3.2.21-beta.4
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.
|
@@ -7,6 +7,29 @@ claude-tools: "Read, Grep, Bash, Glob, Edit, Write, AskUserQuestion, mcp__playwr
|
|
|
7
7
|
copilot-tools: "[read, execute, edit, vscode/askQuestions, playwright/*, appium/*]"
|
|
8
8
|
codex-trigger: "Run when the user asks to RUN, execute, or compile tests, generate selectors.yaml, or run tests. Step 4. Do NOT use for authoring/creating new test cases."
|
|
9
9
|
---
|
|
10
|
+
## ⛔ HARD RULE — the transition INTO this run is a tool call, never prose
|
|
11
|
+
|
|
12
|
+
A QA field report: the user picked "Run test" from create-test's hand-back, and the session
|
|
13
|
+
answered with a BRIEFING — missing selector, expected reds, "run under Node 22" — written as
|
|
14
|
+
"Before you do…", then stopped. Correct facts, wrong role: those are conditions YOU handle
|
|
15
|
+
inside the run, not reasons to stop and hand the work back.
|
|
16
|
+
|
|
17
|
+
- The first thing this command produces is a **tool call** (platform detection, preflight,
|
|
18
|
+
compile — whatever comes first). Never open with a plan and end the turn.
|
|
19
|
+
- A **missing selector** goes to the selector-generation/fix step — that is what this command
|
|
20
|
+
is FOR.
|
|
21
|
+
- **Expected-red scenarios** (@known-defect asserting a live defect) stay red; note them in
|
|
22
|
+
the results summary, never "fix" them and never stop for them.
|
|
23
|
+
- **Runtime selection is yours**: check `node -v` first. If the major version is ≥ 23 and
|
|
24
|
+
Playwright browser runs are known-broken on it, select Node 22 yourself when available —
|
|
25
|
+
`export PATH="$HOME/.nvm/versions/node/$(ls $HOME/.nvm/versions/node | grep '^v22' | tail -1)/bin:$PATH"`
|
|
26
|
+
— and say so in one line. Only if NO compatible Node exists do you stop, with the exact
|
|
27
|
+
install command as the hand-back.
|
|
28
|
+
- Ending this run follows the same law as create-test: the LAST action is the next-step
|
|
29
|
+
hand-back (the AskUserQuestion in "After showing results"), no matter how the run went.
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
10
33
|
## Role
|
|
11
34
|
|
|
12
35
|
You are a **Senior Developer**.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sun-asterisk/sungen",
|
|
3
|
-
"version": "3.2.21-beta.
|
|
3
|
+
"version": "3.2.21-beta.4",
|
|
4
4
|
"description": "Deterministic E2E Test Compiler - Gherkin + Selectors → Playwright tests",
|
|
5
5
|
"main": "src/index.ts",
|
|
6
6
|
"types": "src/index.ts",
|
|
@@ -39,8 +39,8 @@
|
|
|
39
39
|
"@babel/types": "^7.28.5",
|
|
40
40
|
"@cucumber/gherkin": "^37.0.0",
|
|
41
41
|
"@cucumber/messages": "^31.0.0",
|
|
42
|
-
"@sungen/driver-data-factory": "3.2.21-beta.
|
|
43
|
-
"@sungen/driver-ui": "3.2.21-beta.
|
|
42
|
+
"@sungen/driver-data-factory": "3.2.21-beta.4",
|
|
43
|
+
"@sungen/driver-ui": "3.2.21-beta.4",
|
|
44
44
|
"chalk": "^5.6.2",
|
|
45
45
|
"commander": "^14.0.2",
|
|
46
46
|
"dotenv": "^17.2.3",
|
|
@@ -7,6 +7,29 @@ claude-tools: "Read, Grep, Bash, Glob, Edit, Write, AskUserQuestion, mcp__playwr
|
|
|
7
7
|
copilot-tools: "[read, execute, edit, vscode/askQuestions, playwright/*, appium/*]"
|
|
8
8
|
codex-trigger: "Run when the user asks to RUN, execute, or compile tests, generate selectors.yaml, or run tests. Step 4. Do NOT use for authoring/creating new test cases."
|
|
9
9
|
---
|
|
10
|
+
## ⛔ HARD RULE — the transition INTO this run is a tool call, never prose
|
|
11
|
+
|
|
12
|
+
A QA field report: the user picked "Run test" from create-test's hand-back, and the session
|
|
13
|
+
answered with a BRIEFING — missing selector, expected reds, "run under Node 22" — written as
|
|
14
|
+
"Before you do…", then stopped. Correct facts, wrong role: those are conditions YOU handle
|
|
15
|
+
inside the run, not reasons to stop and hand the work back.
|
|
16
|
+
|
|
17
|
+
- The first thing this command produces is a **tool call** (platform detection, preflight,
|
|
18
|
+
compile — whatever comes first). Never open with a plan and end the turn.
|
|
19
|
+
- A **missing selector** goes to the selector-generation/fix step — that is what this command
|
|
20
|
+
is FOR.
|
|
21
|
+
- **Expected-red scenarios** (@known-defect asserting a live defect) stay red; note them in
|
|
22
|
+
the results summary, never "fix" them and never stop for them.
|
|
23
|
+
- **Runtime selection is yours**: check `node -v` first. If the major version is ≥ 23 and
|
|
24
|
+
Playwright browser runs are known-broken on it, select Node 22 yourself when available —
|
|
25
|
+
`export PATH="$HOME/.nvm/versions/node/$(ls $HOME/.nvm/versions/node | grep '^v22' | tail -1)/bin:$PATH"`
|
|
26
|
+
— and say so in one line. Only if NO compatible Node exists do you stop, with the exact
|
|
27
|
+
install command as the hand-back.
|
|
28
|
+
- Ending this run follows the same law as create-test: the LAST action is the next-step
|
|
29
|
+
hand-back (the AskUserQuestion in "After showing results"), no matter how the run went.
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
10
33
|
## Role
|
|
11
34
|
|
|
12
35
|
You are a **Senior Developer**.
|