@qa-gentic/stlc-agents 1.0.20 → 1.0.22
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/ORCHESTRATION_RULES.md +4 -0
- package/package.json +1 -1
- package/src/cli/cmd-mcp-config.js +0 -11
package/ORCHESTRATION_RULES.md
CHANGED
|
@@ -74,6 +74,7 @@ stubs and then acknowledge the violation — it must prevent them before generat
|
|
|
74
74
|
- If a step cannot produce a complete output, declare it `[!] blocked` and stop.
|
|
75
75
|
- Partial outputs passed downstream cause compounding failures and wasted tokens.
|
|
76
76
|
|
|
77
|
+
|
|
77
78
|
**Countable verification pattern (required for code generation steps):**
|
|
78
79
|
```
|
|
79
80
|
Expected: [N] step definitions (from scenario_inventory)
|
|
@@ -81,6 +82,9 @@ Generating: [N] step definitions
|
|
|
81
82
|
Verify after: count implemented bodies — must equal [N], zero empty
|
|
82
83
|
```
|
|
83
84
|
|
|
85
|
+
**Gherkin Scenario Mapping Rule:**
|
|
86
|
+
Gherkin scenarios must be derived from acceptance criteria and the real user flow (as mapped in the flow map), not from the manual test case list. There is no enforced 1:1 mapping between manual test cases and Gherkin scenarios. Scenarios should cover all acceptance criteria, boundary cases, and negative paths, but may combine or split flows as needed for clarity and maintainability.
|
|
87
|
+
|
|
84
88
|
### 2.6 Query-Driven Data Capture (Snapshot / Scraping Steps)
|
|
85
89
|
|
|
86
90
|
- Navigation is NOT the deliverable — **structured data extraction** is.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@qa-gentic/stlc-agents",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.22",
|
|
4
4
|
"description": "QA STLC Agents — five MCP servers + skills for AI-powered test case, Gherkin, Playwright generation, and Helix-QA file writing against Azure DevOps and Jira Cloud. Full pipeline for both: fetch → test cases → Gherkin → Playwright → Helix-QA. Works with Claude Code, GitHub Copilot, Cursor, Windsurf.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"playwright",
|
|
@@ -192,16 +192,12 @@ function buildVscodeConfig(pythonBin, playwrightPort, integration) {
|
|
|
192
192
|
servers[name] = {
|
|
193
193
|
type: "stdio",
|
|
194
194
|
command: bin,
|
|
195
|
-
args: [],
|
|
196
|
-
env: { ...COST_ENV },
|
|
197
195
|
};
|
|
198
196
|
} else {
|
|
199
197
|
missing.push(name);
|
|
200
198
|
servers[name] = {
|
|
201
199
|
type: "stdio",
|
|
202
200
|
command: `/path/to/.venv/bin/${name}`,
|
|
203
|
-
args: [],
|
|
204
|
-
env: { ...COST_ENV },
|
|
205
201
|
"_comment": "NOT FOUND — run: pip install qa-gentic-stlc-agents",
|
|
206
202
|
};
|
|
207
203
|
}
|
|
@@ -213,19 +209,12 @@ function buildVscodeConfig(pythonBin, playwrightPort, integration) {
|
|
|
213
209
|
servers[JIRA_AGENT_NAME] = {
|
|
214
210
|
type: "stdio",
|
|
215
211
|
command: jiraBin,
|
|
216
|
-
args: [],
|
|
217
|
-
env: {
|
|
218
|
-
...COST_ENV,
|
|
219
|
-
...JIRA_ENV_VARS,
|
|
220
|
-
},
|
|
221
212
|
};
|
|
222
213
|
} else {
|
|
223
214
|
missing.push(JIRA_AGENT_NAME);
|
|
224
215
|
servers[JIRA_AGENT_NAME] = {
|
|
225
216
|
type: "stdio",
|
|
226
217
|
command: `/path/to/.venv/bin/${JIRA_AGENT_NAME}`,
|
|
227
|
-
args: [],
|
|
228
|
-
env: { ...COST_ENV, ...JIRA_ENV_VARS },
|
|
229
218
|
"_comment": "NOT FOUND — run: pip install qa-gentic-stlc-agents",
|
|
230
219
|
};
|
|
231
220
|
}
|