qatools-cli 1.2.10 → 1.2.11
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 +1 -1
- package/qatools.js +92 -2
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "qatools-cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.11",
|
|
4
4
|
"description": "CLI for QA Tools — requirements, epics, sprints, sessions, App Context sync, project agenda. The companion to qa-tools.com.",
|
|
5
5
|
"scripts": {
|
|
6
6
|
"release": "npm version patch --no-git-tag-version && npm publish",
|
package/qatools.js
CHANGED
|
@@ -2619,6 +2619,10 @@ You generate test protocols (templates) from approved requirements.
|
|
|
2619
2619
|
## Rules
|
|
2620
2620
|
- Every test MUST have requirementKey, requirementVersion, and purpose
|
|
2621
2621
|
- Generate from BOTH acceptance criteria AND negative scenarios
|
|
2622
|
+
|
|
2623
|
+
## Manual versus automated
|
|
2624
|
+
A test protocol is run by people. Put in it only what a person must check because you can't verify it yourself: look and feel, real mobile devices, e-mail/SMS actually arriving, BankID/Freja, printing/PDF, flows between several parties. Say in purpose why a person must do it. What you can verify yourself belongs in automated tests in the code (results reach qa-tools via \`qatools test-report\`).
|
|
2625
|
+
When planning a sprint, draft one such protocol per sprint (MCP: testProtocols in propose_sprint_plan, or create_test_protocol after a plan approved in the conversation). You never approve a protocol — a project member does.
|
|
2622
2626
|
`,
|
|
2623
2627
|
|
|
2624
2628
|
"qa-test-analyst.md": `---
|
|
@@ -3761,9 +3765,51 @@ const mcpTools = [
|
|
|
3761
3765
|
description: "Requirements deliberately left out, with why",
|
|
3762
3766
|
items: { type: "object", properties: { key: mcpStr("Requirement key"), reason: mcpStr("Why") }, required: ["key", "reason"], additionalProperties: false },
|
|
3763
3767
|
},
|
|
3768
|
+
testProtocols: {
|
|
3769
|
+
type: "array",
|
|
3770
|
+
description: "One manual test protocol per target sprint: only tests a person must perform (you can't verify them yourself). Each test's requirementKey must be planned in that sprint by this proposal. Approved together with the proposal.",
|
|
3771
|
+
items: {
|
|
3772
|
+
type: "object",
|
|
3773
|
+
properties: {
|
|
3774
|
+
name: mcpStr("Protocol name, e.g. 'Release 4.1 — manual tests'"),
|
|
3775
|
+
sprintId: mcpStr("Existing sprint ID (or use newSprintRef)"),
|
|
3776
|
+
newSprintRef: mcpStr("ref of a sprint in newSprints"),
|
|
3777
|
+
sections: {
|
|
3778
|
+
type: "array",
|
|
3779
|
+
description: "Sections of manual tests",
|
|
3780
|
+
items: {
|
|
3781
|
+
type: "object",
|
|
3782
|
+
properties: {
|
|
3783
|
+
title: mcpStr("Section title"),
|
|
3784
|
+
tests: {
|
|
3785
|
+
type: "array",
|
|
3786
|
+
items: {
|
|
3787
|
+
type: "object",
|
|
3788
|
+
properties: {
|
|
3789
|
+
id: mcpStr("Test id, e.g. M-1"),
|
|
3790
|
+
name: mcpStr("What is tested"),
|
|
3791
|
+
steps: mcpStr("Steps a person follows"),
|
|
3792
|
+
expected: mcpStr("Expected result"),
|
|
3793
|
+
purpose: mcpStr("Why a person must perform this, e.g. 'real phone camera', 'SMS must actually arrive', 'visual check'"),
|
|
3794
|
+
requirementKey: mcpStr("Key of the requirement it verifies"),
|
|
3795
|
+
},
|
|
3796
|
+
required: ["name", "steps", "expected", "purpose", "requirementKey"],
|
|
3797
|
+
additionalProperties: false,
|
|
3798
|
+
},
|
|
3799
|
+
},
|
|
3800
|
+
},
|
|
3801
|
+
required: ["title", "tests"],
|
|
3802
|
+
additionalProperties: false,
|
|
3803
|
+
},
|
|
3804
|
+
},
|
|
3805
|
+
},
|
|
3806
|
+
required: ["name", "sections"],
|
|
3807
|
+
additionalProperties: false,
|
|
3808
|
+
},
|
|
3809
|
+
},
|
|
3764
3810
|
}, ["items"]),
|
|
3765
3811
|
run: async (a) => {
|
|
3766
|
-
const r = await mcpCall("createPlanProposal", { projectId: a.projectId, ...mcpPick(a, ["goal", "summary", "items", "newSprints", "omitted"]) });
|
|
3812
|
+
const r = await mcpCall("createPlanProposal", { projectId: a.projectId, ...mcpPick(a, ["goal", "summary", "items", "newSprints", "omitted", "testProtocols"]) });
|
|
3767
3813
|
return { ...r, next: "Pending. A project member approves or rejects it in qa-tools under Sprints → Plan proposals." };
|
|
3768
3814
|
},
|
|
3769
3815
|
},
|
|
@@ -3910,6 +3956,49 @@ const mcpTools = [
|
|
|
3910
3956
|
return { updated: a.itemId, fields: Object.keys(u) };
|
|
3911
3957
|
},
|
|
3912
3958
|
},
|
|
3959
|
+
{
|
|
3960
|
+
name: "create_test_protocol",
|
|
3961
|
+
description: "Create a sprint's manual test protocol after a plan was approved in this conversation (sprint.ai-planning-manual-tests). Only tests a person must perform — what you can verify yourself belongs in automated tests in the code. It is saved for review (pending_review); a project member approves it under Test protocols, never you.",
|
|
3962
|
+
inputSchema: mcpSchema({
|
|
3963
|
+
sprintId: mcpStr("Sprint ID the protocol belongs to"),
|
|
3964
|
+
name: mcpStr("Protocol name, e.g. 'Release 4.1 — manual tests'"),
|
|
3965
|
+
sections: {
|
|
3966
|
+
type: "array",
|
|
3967
|
+
description: "Sections of manual tests",
|
|
3968
|
+
items: {
|
|
3969
|
+
type: "object",
|
|
3970
|
+
properties: {
|
|
3971
|
+
title: mcpStr("Section title"),
|
|
3972
|
+
tests: {
|
|
3973
|
+
type: "array",
|
|
3974
|
+
items: {
|
|
3975
|
+
type: "object",
|
|
3976
|
+
properties: {
|
|
3977
|
+
id: mcpStr("Test id, e.g. M-1"),
|
|
3978
|
+
name: mcpStr("What is tested"),
|
|
3979
|
+
steps: mcpStr("Steps a person follows"),
|
|
3980
|
+
expected: mcpStr("Expected result"),
|
|
3981
|
+
purpose: mcpStr("Why a person must perform this, e.g. 'real phone camera', 'SMS must actually arrive', 'visual check'"),
|
|
3982
|
+
requirementKey: mcpStr("Key of the requirement it verifies"),
|
|
3983
|
+
},
|
|
3984
|
+
required: ["name", "steps", "expected", "purpose", "requirementKey"],
|
|
3985
|
+
additionalProperties: false,
|
|
3986
|
+
},
|
|
3987
|
+
},
|
|
3988
|
+
},
|
|
3989
|
+
required: ["title", "tests"],
|
|
3990
|
+
additionalProperties: false,
|
|
3991
|
+
},
|
|
3992
|
+
},
|
|
3993
|
+
}, ["sprintId", "name", "sections"]),
|
|
3994
|
+
run: async (a) => {
|
|
3995
|
+
for (const sec of a.sections) for (const t of sec.tests || []) {
|
|
3996
|
+
if (!String(t.purpose || "").trim()) throw new McpToolError(`Test "${t.name}" needs a purpose saying why a person must perform it`);
|
|
3997
|
+
}
|
|
3998
|
+
const r = await mcpCall("uploadTemplate", { projectId: a.projectId, sprintId: a.sprintId, name: a.name, sections: a.sections });
|
|
3999
|
+
return { ...r, next: "Pending review. A project member approves it in qa-tools under Test protocols." };
|
|
4000
|
+
},
|
|
4001
|
+
},
|
|
3913
4002
|
{
|
|
3914
4003
|
name: "list_templates",
|
|
3915
4004
|
description: "List test templates (test protocols) and their review status.",
|
|
@@ -3992,7 +4081,8 @@ Follow these steps in order:
|
|
|
3992
4081
|
4. STOP and ask the user: approve here, or save it as a proposal to decide later in qa-tools? Change nothing before that. Apply any adjustments the user asks for and show the table again.
|
|
3993
4082
|
- If nobody is there to answer (an unattended run), or the user chooses "later": call propose_sprint_plan with the same rows, and report the result. Do not apply anything yourself.
|
|
3994
4083
|
5. After approval in this conversation: create_sprint for any new sprints, then update_requirement with sprintId for each planned requirement. Report each change and any refusal verbatim — never retry a refused change in a different way.
|
|
3995
|
-
6.
|
|
4084
|
+
6. Manual tests, per sprint: draft a test protocol with the tests a person must perform because you can't verify them yourself — look and feel, real mobile devices, e-mail/SMS actually arriving, BankID/Freja, printing/PDF, flows between several parties. Each test has requirementKey (a requirement planned in that sprint) and a purpose saying why a person must do it. What you can verify yourself goes into automated tests in the code, not here. Show the tests with the plan. With propose_sprint_plan, pass them as testProtocols (approved together with the proposal). After approval in the conversation, save each with create_test_protocol (pending review — a member approves it). A sprint with nothing that needs a person gets no protocol; say so.
|
|
4085
|
+
7. End with get_sprint_items for each affected sprint so the user can see the result.`,
|
|
3996
4086
|
},
|
|
3997
4087
|
{
|
|
3998
4088
|
name: "daily_agenda_run",
|