qatools-cli 1.2.7 → 1.2.9
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 +18 -10
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "qatools-cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.9",
|
|
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
|
@@ -1043,7 +1043,7 @@ program
|
|
|
1043
1043
|
} else {
|
|
1044
1044
|
console.log(`\n${reqs.length} requirement${reqs.length !== 1 ? 's' : ''}:\n`);
|
|
1045
1045
|
for (const r of reqs) {
|
|
1046
|
-
const badge = r.status === "rejected" ? "❌" : r.status === "approved" ? "✅" : r.status === "tested" ? "🟢" : r.status === "implemented" ? "🟡" : r.status === "superseded" ? "🗑" : "📝";
|
|
1046
|
+
const badge = r.status === "rejected" ? "❌" : r.status === "approved" ? "✅" : r.status === "in_progress" ? "🔨" : r.status === "tested" ? "🟢" : r.status === "implemented" ? "🟡" : r.status === "superseded" ? "🗑" : "📝";
|
|
1047
1047
|
const epic = r.epicKey ? ` epic:${r.epicKey}` : ' (no epic)';
|
|
1048
1048
|
console.log(` ${badge} [${r.key}]${epic} ${r.title} (${r.status})`);
|
|
1049
1049
|
if (r.reviewComment) console.log(` 💬 ${r.reviewComment}`);
|
|
@@ -1457,7 +1457,8 @@ program
|
|
|
1457
1457
|
.description("Update one or more requirements (by id, optionally from a JSON file). status=implemented/tested REQUIRES --evidence.")
|
|
1458
1458
|
.option("-f, --file <path>", "JSON file with updates: { '<requirementId>': { status, epicKey, evidence, ... } }")
|
|
1459
1459
|
.option("-i, --id <id>", "Single requirement ID to update")
|
|
1460
|
-
.option("--status <status>", "New status (draft/approved/rejected/implemented/tested/superseded)")
|
|
1460
|
+
.option("--status <status>", "New status (draft/approved/in_progress/rejected/implemented/tested/superseded)")
|
|
1461
|
+
.option("--assigned <email>", "Set assignee: a member's email, 'me' (you, or the Claude account for an API key), or empty string to clear")
|
|
1461
1462
|
.option("--evidence <text>", "REQUIRED when status=implemented or tested. Cite test output, file:line, expected vs actual, or 'no test applies because <reason>'.")
|
|
1462
1463
|
.option("--attach <files...>", "Image file(s) as evidence (png/jpg/webp/gif, max 4 MB each)")
|
|
1463
1464
|
.option("--epic <key>", "Set epicKey")
|
|
@@ -1489,6 +1490,7 @@ program
|
|
|
1489
1490
|
} else if (options.id) {
|
|
1490
1491
|
const u = {};
|
|
1491
1492
|
if (options.status) u.status = options.status;
|
|
1493
|
+
if (options.assigned !== undefined) u.assignedTo = options.assigned;
|
|
1492
1494
|
if (options.epic !== undefined) u.epicKey = options.epic;
|
|
1493
1495
|
if (options.sprint !== undefined) u.sprintId = options.sprint;
|
|
1494
1496
|
if (options.type) u.type = options.type;
|
|
@@ -2539,22 +2541,26 @@ App Context → Epics → Requirements → Sprint → Implementation → Test
|
|
|
2539
2541
|
\`qatools context\`
|
|
2540
2542
|
\`qatools requirements --status approved -o requirements.json\`
|
|
2541
2543
|
|
|
2542
|
-
2.
|
|
2544
|
+
2. Before you start on a requirement, mark it in progress so others can see who works on it:
|
|
2545
|
+
\`qatools requirement-update -i <requirementId> --status in_progress --assigned me\`
|
|
2546
|
+
|
|
2547
|
+
3. Implement according to acceptanceCriteria AND negativeCriteria.
|
|
2543
2548
|
Every piece of code must be traceable to a requirementKey.
|
|
2549
|
+
When done and verified: \`--status implemented --evidence "<verification>"\`. If you stop without finishing, set it back to \`approved\` (clears the assignee).
|
|
2544
2550
|
|
|
2545
|
-
|
|
2551
|
+
4. If you discover something unexpected during implementation:
|
|
2546
2552
|
- Behavior doesn't match a requirement → create AVV: \`qatools backlog-create -d "..." -t bug --requirement-key <key>\`
|
|
2547
2553
|
- Requirement is missing or unclear → create GAP: \`qatools backlog-create -d "..." -t requirement_gap --requirement-key <key>\`
|
|
2548
2554
|
- Technical issue (infra, runtime) → create DEF: \`qatools backlog-create -d "..." -t technical_defect\`
|
|
2549
2555
|
- Improvement idea → create IMP: \`qatools backlog-create -d "..." -t improvement\`
|
|
2550
2556
|
|
|
2551
|
-
|
|
2557
|
+
5. NEVER create requirements directly as backlog items. If a GAP needs to become a requirement, flag it — the user decides.
|
|
2552
2558
|
|
|
2553
|
-
|
|
2559
|
+
6. Check for pending test sessions:
|
|
2554
2560
|
\`qatools pending\`
|
|
2555
2561
|
\`qatools read-session -s <id> -o session.json\`
|
|
2556
2562
|
|
|
2557
|
-
|
|
2563
|
+
7. If tests fail, analyze and fix:
|
|
2558
2564
|
\`qatools upload-analysis -s <id> -f analysis.json\`
|
|
2559
2565
|
|
|
2560
2566
|
## Rules
|
|
@@ -3508,6 +3514,7 @@ const MCP_INSTRUCTIONS = `qa-tools: requirements-driven QA. Rules that apply to
|
|
|
3508
3514
|
- The backlog is signals (bug=AVV, requirement_gap=GAP, technical_defect=DEF, improvement=IMP), not a task list.
|
|
3509
3515
|
- Backlog flow: open → in_progress → ready_for_test → resolved. Set ready_for_test when you believe a fix is done; resolved needs evidence (min 10 chars) and, except GAP, a prior ready_for_test.
|
|
3510
3516
|
- Requirement status implemented/tested needs evidence: test output, file:line, expected vs actual, or "no test applies because <reason>".
|
|
3517
|
+
- Requirement flow: approved → in_progress → implemented → tested. When you start implementing an approved requirement, set status in_progress and assignedTo "me" (update_requirement); if you stop without finishing, set it back to approved.
|
|
3511
3518
|
- Sprint planning: plan approved, functional requirements only (update_requirement sprintId), never backlog items; non-functional requirements are continuous and never go into sprints. Gather facts first (list_sprints, sprint_velocity, list_epics, list_requirements), respect epic dependsOn, present the plan as a table (sprint | requirement | reason) and change NOTHING until the user approves it in this conversation. If the user isn't here or wants to decide later, save it with propose_sprint_plan instead — they approve in qa-tools. Full procedure: prompt plan_sprints.
|
|
3512
3519
|
- Every tool takes an optional projectId; without it the configured project (qatools setup) is used.`;
|
|
3513
3520
|
|
|
@@ -3516,7 +3523,7 @@ const mcpInt = (description, extra = {}) => ({ type: "integer", description, ...
|
|
|
3516
3523
|
const mcpBool = (description) => ({ type: "boolean", description });
|
|
3517
3524
|
const mcpStrArray = (description, items = { type: "string" }) => ({ type: "array", items, description });
|
|
3518
3525
|
const MCP_PROJECT_PROP = { projectId: mcpStr("Project ID. Defaults to the configured project.") };
|
|
3519
|
-
const MCP_REQ_STATUSES = ["draft", "approved", "rejected", "implemented", "tested", "superseded"];
|
|
3526
|
+
const MCP_REQ_STATUSES = ["draft", "approved", "in_progress", "rejected", "implemented", "tested", "superseded"];
|
|
3520
3527
|
const MCP_BACKLOG_STATUSES = ["open", "in_progress", "ready_for_test", "resolved", "rejected"];
|
|
3521
3528
|
const MCP_BACKLOG_TYPES = ["bug", "improvement", "requirement_gap", "technical_defect"];
|
|
3522
3529
|
const MCP_PRIORITY = mcpInt("Priority: 1 (high), 2 (medium), 3 (low)", { enum: [1, 2, 3] });
|
|
@@ -3600,10 +3607,11 @@ const mcpTools = [
|
|
|
3600
3607
|
},
|
|
3601
3608
|
{
|
|
3602
3609
|
name: "update_requirement",
|
|
3603
|
-
description: "Update a requirement (status, epic, sprint, text). status implemented/tested REQUIRES evidence. Set sprintId to plan the requirement in a sprint, or empty string to unplan it.",
|
|
3610
|
+
description: "Update a requirement (status, assignee, epic, sprint, text). status implemented/tested REQUIRES evidence. When you start implementing an approved requirement, set status in_progress and assignedTo \"me\". Set sprintId to plan the requirement in a sprint, or empty string to unplan it.",
|
|
3604
3611
|
inputSchema: mcpSchema({
|
|
3605
3612
|
requirementId: mcpStr("Requirement document ID"),
|
|
3606
3613
|
status: mcpStr("New status", { enum: MCP_REQ_STATUSES }),
|
|
3614
|
+
assignedTo: mcpStr("Assignee: a member's email, \"me\" (the Claude account), or empty string to clear. Setting status back to approved clears it."),
|
|
3607
3615
|
evidence: mcpStr("Required for implemented/tested (min 10 chars): test output, file:line, expected vs actual, or 'no test applies because <reason>'"),
|
|
3608
3616
|
epicKey: mcpStr("Epic key"),
|
|
3609
3617
|
sprintId: mcpStr("Sprint ID (empty string clears)"),
|
|
@@ -3614,7 +3622,7 @@ const mcpTools = [
|
|
|
3614
3622
|
attachments: mcpStrArray("Local image file paths (png/jpg/webp/gif, max 4 MB) to attach to the evidence, e.g. screenshots"),
|
|
3615
3623
|
}, ["requirementId"]),
|
|
3616
3624
|
run: async (a) => {
|
|
3617
|
-
const updates = mcpPick(a, ["status", "epicKey", "sprintId", "type", "title", "description", "acceptanceCriteria"]);
|
|
3625
|
+
const updates = mcpPick(a, ["status", "assignedTo", "epicKey", "sprintId", "type", "title", "description", "acceptanceCriteria"]);
|
|
3618
3626
|
if (Object.keys(updates).length === 0) throw new McpToolError("No fields to update.");
|
|
3619
3627
|
const evidenceById = a.evidence ? { [a.requirementId]: a.evidence } : {};
|
|
3620
3628
|
if (requirementEvidenceViolations({ [a.requirementId]: updates }, evidenceById).length > 0) {
|