@teevee98/synapse-hub 4.2.0 → 4.2.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/.agents/skills/01-web-automation/auth-session-and-cookie-manager/SKILL.md +46 -2
- package/.agents/skills/01-web-automation/bats-testing-patterns/SKILL.md +49 -4
- package/.agents/skills/01-web-automation/clean-pom-crafter/SKILL.md +56 -66
- package/.agents/skills/01-web-automation/e2e-testing-patterns/SKILL.md +48 -3
- package/.agents/skills/01-web-automation/katalon-cli-runner/SKILL.md +56 -11
- package/.agents/skills/01-web-automation/lam-script-generator/SKILL.md +49 -7
- package/.agents/skills/01-web-automation/mobile-appium-som/SKILL.md +54 -11
- package/.agents/skills/01-web-automation/playwright-live-interaction/SKILL.md +48 -90
- package/.agents/skills/01-web-automation/playwright-webapp-testing/SKILL.md +53 -10
- package/.agents/skills/01-web-automation/web-agent-gym-benchmarking/SKILL.md +44 -3
- package/.agents/skills/02-test-design/architecture-decision-records/SKILL.md +49 -8
- package/.agents/skills/02-test-design/gherkin-to-suite/SKILL.md +49 -8
- package/.agents/skills/02-test-design/rbt-manual-testing/SKILL.md +49 -7
- package/.agents/skills/02-test-design/review-spec/SKILL.md +46 -5
- package/.agents/skills/02-test-design/tot-exploratory-testing/SKILL.md +44 -3
- package/.agents/skills/03-api-and-contracts/api-network-mocking-interception/SKILL.md +50 -4
- package/.agents/skills/03-api-and-contracts/api-spec-to-e2e-matrix/SKILL.md +47 -6
- package/.agents/skills/03-api-and-contracts/consumer-driven-contract-testing/SKILL.md +79 -34
- package/.agents/skills/04-performance-and-load/backend-load-and-stress-patterns/SKILL.md +47 -4
- package/.agents/skills/04-performance-and-load/lean-impact-scoreboard/SKILL.md +46 -5
- package/.agents/skills/04-performance-and-load/web-vitals-and-performance-profiler/SKILL.md +44 -2
- package/.agents/skills/05-security-and-compliance/security-dast-sentinel/SKILL.md +57 -13
- package/.agents/skills/05-security-and-compliance/skillspector-security-guard/SKILL.md +45 -4
- package/.agents/skills/05-security-and-compliance/wcag-audit-patterns/SKILL.md +48 -3
- package/.agents/skills/06-healing-and-resilience/agentless-qa-repair/SKILL.md +45 -4
- package/.agents/skills/06-healing-and-resilience/antigravity-test-sentinel/SKILL.md +47 -5
- package/.agents/skills/06-healing-and-resilience/failure-autopsy-and-healing/SKILL.md +48 -7
- package/.agents/skills/06-healing-and-resilience/flaky-test-sentinel-and-quarantine/SKILL.md +54 -23
- package/.agents/skills/06-healing-and-resilience/self-healing-locator/SKILL.md +46 -5
- package/.agents/skills/06-healing-and-resilience/systematic-debugging/SKILL.md +50 -9
- package/.agents/skills/06-healing-and-resilience/test-driven-development/SKILL.md +52 -11
- package/.agents/skills/06-healing-and-resilience/verification-before-completion/SKILL.md +52 -11
- package/.agents/skills/06-healing-and-resilience/visual-regression-sentinel/SKILL.md +47 -4
- package/.agents/skills/07-data-and-state/db-state-verifier-and-seeder/SKILL.md +50 -4
- package/.agents/skills/07-data-and-state/file-and-report-validator/SKILL.md +47 -3
- package/.agents/skills/07-data-and-state/synthetic-test-data-generator/SKILL.md +52 -4
- package/.agents/skills/08-code-quality/code-refactoring-refactor-clean/SKILL.md +51 -10
- package/.agents/skills/08-code-quality/graphify-impact-analyzer/SKILL.md +78 -34
- package/.agents/skills/08-code-quality/graphify-impact-analyzer/examples/dependency_blast_radius.json +3 -4
- package/.agents/skills/08-code-quality/lean-code-ladder/SKILL.md +49 -9
- package/.agents/skills/08-code-quality/repo-quality-audit/SKILL.md +45 -5
- package/.agents/skills/08-code-quality/senior-code-review/SKILL.md +48 -6
- package/.agents/skills/08-code-quality/surgical-coding-principles/SKILL.md +49 -9
- package/.agents/skills/08-code-quality/technical-debt-harvester/SKILL.md +47 -4
- package/.agents/skills/09-ci-and-devops/github-actions-templates/SKILL.md +48 -16
- package/.agents/skills/09-ci-and-devops/github-actions-templates/examples/matrix_test_pipeline.yml +2 -1
- package/.agents/skills/10-agent-orchestration/actor-qa-swarm/SKILL.md +44 -3
- package/.agents/skills/10-agent-orchestration/agent-orchestration-multi-agent-optimize/SKILL.md +47 -6
- package/.agents/skills/10-agent-orchestration/event-stream-qa-orchestrator/SKILL.md +44 -3
- package/.agents/skills/10-agent-orchestration/persistent-planning-files/SKILL.md +52 -12
- package/.agents/skills/10-agent-orchestration/qa-memory-os/SKILL.md +45 -4
- package/.agents/skills/11-ai-and-prompting/meta-prompt-crafter/SKILL.md +51 -9
- package/.agents/skills/11-ai-and-prompting/mipro-prompt-compiler/SKILL.md +44 -3
- package/.agents/skills/11-ai-and-prompting/qa-aci-interface/SKILL.md +44 -3
- package/.agents/skills/11-ai-and-prompting/token-and-context-optimizer/SKILL.md +49 -8
- package/.cursor/rules/synapse-qa.mdc +20 -7
- package/.cursorrules +19 -5
- package/.windsurfrules +18 -3
- package/AGENTS.md +51 -65
- package/CLAUDE.md +38 -24
- package/README.en.md +2 -2
- package/README.md +2 -2
- package/agentskills.json +1 -1
- package/docs/ARCHITECTURE.en.md +1 -1
- package/docs/ARCHITECTURE.md +1 -1
- package/docs/CLIENT_SUPPORT_MATRIX.md +44 -0
- package/docs/SIDE_EFFECTING_TOOLS_INVENTORY.md +233 -0
- package/package.json +1 -1
- package/plugin.json +1 -1
- package/skills_manifest.json +1 -1
- package/synapse.config.json +1 -1
- package/templates/ai_bridges/CLAUDE.md +29 -26
- package/templates/ai_bridges/copilot-instructions.md +14 -5
- package/templates/ai_bridges/cursor_synapse_qa.mdc +16 -7
- package/templates/ai_bridges/windsurfrules +14 -3
- package/tools/TOOLS_RUNBOOK.md +1 -1
- package/tools/__init__.py +1 -1
- package/tools/api_fuzzer.py +295 -41
- package/tools/benchmark_swarm_context.py +11 -4
- package/tools/browser_helpers.js +2 -2
- package/tools/cli.py +4 -4
- package/tools/core/bm25_retriever.py +1 -1
- package/tools/core/i18n.py +1 -1
- package/tools/core/provider_usage_adapter.py +66 -0
- package/tools/core/token_estimator.py +39 -1
- package/tools/count_tokens.py +2 -2
- package/tools/dashboard_generator.py +8 -8
- package/tools/db_sandbox.py +182 -43
- package/tools/distill_log.py +1 -1
- package/tools/distill_skill.py +17 -2
- package/tools/git_pre_commit_guard.py +190 -1
- package/tools/mcp_docx_server.py +1 -1
- package/tools/mcp_excel_server.py +1 -1
- package/tools/mcp_server.py +33 -5
- package/tools/micro_mutator.py +30 -1
- package/tools/pentest_scope_guard.py +288 -15
- package/tools/project_state.py +29 -5
- package/tools/reversible_sandbox.py +58 -13
- package/tools/rules_router.py +80 -27
- package/tools/skill_canonical_digest.py +60 -2
- package/tools/sync_agent_rules.py +187 -61
- package/tools/task_memory_manager.py +16 -1
- package/tools/ui_server.py +3 -1
- package/tools/update_sentinel.py +3 -3
- package/tools/validate_skills_schema.py +349 -56
- package/tools/verify_all.py +96 -2
- package/tools/welcome_page.py +1 -1
|
@@ -10,11 +10,35 @@ policies:
|
|
|
10
10
|
---
|
|
11
11
|
# Architecture Decision Records (ADR) Skill
|
|
12
12
|
|
|
13
|
+
> **Author Attribution & MIT License Guard:** Synapse Hub is open-source software created by **Thế Vị (@TeeVee98)** (<https://github.com/TeeVee98/Synapse-Hub>) under the MIT License.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## 1. Trigger & Activation
|
|
18
|
+
|
|
19
|
+
- **Trigger Clause:** Record, structure, and maintain technical Architecture Decision Records (ADRs). Use when documenting significant architecture decisions as ADRs.
|
|
20
|
+
- **Activation Scope:** Domain workflows for `02-test-design` involving `architecture-decision-records`.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. Non-Goals & Boundary Constraints
|
|
25
|
+
|
|
26
|
+
- **What NOT to do:**
|
|
27
|
+
- Do NOT use ADRs for trivial code refactoring or minor variable renames; ADRs are for architectural decisions.
|
|
28
|
+
- Do NOT leave ADRs in ambiguous states; follow explicit lifecycle statuses (PROPOSED, ACCEPTED, DEPRECATED, SUPERSEDED).
|
|
29
|
+
- Do NOT omit negative consequences or tradeoffs in the decision record.
|
|
30
|
+
- **Sibling Skill Boundaries:**
|
|
31
|
+
- review-spec audits functional specifications; architecture-decision-records captures strategic technical and architectural choices.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## 3. Ordered Execution Workflow
|
|
36
|
+
|
|
13
37
|
> **Target:** Standardize technical decision logs, architectural trade-offs, and design rationale across enterprise testing platforms.
|
|
14
38
|
|
|
15
39
|
---
|
|
16
40
|
|
|
17
|
-
|
|
41
|
+
### When to Use
|
|
18
42
|
|
|
19
43
|
- Documenting significant framework, toolchain, or database decisions.
|
|
20
44
|
- Recording architecture changes (e.g. Clean POM flat architecture vs BDD layer).
|
|
@@ -23,7 +47,7 @@ policies:
|
|
|
23
47
|
|
|
24
48
|
---
|
|
25
49
|
|
|
26
|
-
|
|
50
|
+
### ADR Lifecycle State Machine
|
|
27
51
|
|
|
28
52
|
```mermaid
|
|
29
53
|
stateDiagram-v2
|
|
@@ -35,26 +59,27 @@ stateDiagram-v2
|
|
|
35
59
|
|
|
36
60
|
---
|
|
37
61
|
|
|
38
|
-
|
|
62
|
+
### Standard Lightweight ADR Format
|
|
39
63
|
|
|
40
64
|
Create decision records inside `docs/adr/ADR-XXXX-<title>.md`:
|
|
41
65
|
|
|
66
|
+
<!-- classification: illustrative -->
|
|
42
67
|
```markdown
|
|
43
68
|
# ADR-0001: Adopt Clean POM Flat Architecture
|
|
44
69
|
|
|
45
|
-
|
|
70
|
+
### Status
|
|
46
71
|
Accepted
|
|
47
72
|
|
|
48
|
-
|
|
73
|
+
### Context
|
|
49
74
|
E2E automated test suites suffered from high maintenance overhead, locator duplication, and flaky runs caused by deeply nested inheritance hierarchies and raw selectors scattered across test scripts.
|
|
50
75
|
|
|
51
|
-
|
|
76
|
+
### Decision
|
|
52
77
|
Enforce a 2-tier Clean Page Object Model:
|
|
53
78
|
1. All test scripts live in `tests/` and contain only business action calls.
|
|
54
79
|
2. All locators and DOM operations live in Page Classes inheriting directly from `BasePage`.
|
|
55
80
|
3. Raw XPaths and CSS selectors are strictly prohibited in test scripts.
|
|
56
81
|
|
|
57
|
-
|
|
82
|
+
### Consequences
|
|
58
83
|
- **Positive:** Zero locator duplication, modular self-healing, faster onboarding.
|
|
59
84
|
- **Negative:** Requires refactoring legacy tests to encapsulate DOM calls into Page Classes.
|
|
60
85
|
- **Compliance:** Enforced in CI via `tools/verify_all.py` (Gate 3).
|
|
@@ -62,8 +87,24 @@ Enforce a 2-tier Clean Page Object Model:
|
|
|
62
87
|
|
|
63
88
|
---
|
|
64
89
|
|
|
65
|
-
|
|
90
|
+
### Best Practices
|
|
66
91
|
|
|
67
92
|
- Keep ADRs concise (< 500 words per decision).
|
|
68
93
|
- Store ADRs as markdown versioned alongside code in `docs/adr/`.
|
|
69
94
|
- Never modify an accepted ADR to change history; author a new ADR that supersedes the previous one.
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
## 4. Verification Points & DoD
|
|
99
|
+
|
|
100
|
+
1. ADR file created in `docs/adr/` with standard lightweight format (Title, Status, Context, Decision, Consequences).
|
|
101
|
+
2. Status transitions adhere to ADR lifecycle state machine.
|
|
102
|
+
3. Consequences section explicitly lists tradeoffs and negative side effects.
|
|
103
|
+
|
|
104
|
+
---
|
|
105
|
+
|
|
106
|
+
## 5. Handoff Protocol
|
|
107
|
+
|
|
108
|
+
- **Deliverables:** Structured ADR document (`docs/adr/NNNN-*.md`) and updated ADR index.
|
|
109
|
+
- **Next Subagent:** orchestrator
|
|
110
|
+
- **Output Format:** Clean POM code, structured JSON telemetry, or validated markdown handoff.
|
|
@@ -10,6 +10,30 @@ policies:
|
|
|
10
10
|
---
|
|
11
11
|
# Gherkin to Suite Compiler — Natural-Language Test Ingestion (0-Token)
|
|
12
12
|
|
|
13
|
+
> **Author Attribution & MIT License Guard:** Synapse Hub is open-source software created by **Thế Vị (@TeeVee98)** (<https://github.com/TeeVee98/Synapse-Hub>) under the MIT License.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## 1. Trigger & Activation
|
|
18
|
+
|
|
19
|
+
- **Trigger Clause:** Compile Gherkin .feature files into an expanded test matrix, hub Universal IR and a proven-vs-owed coverage-gap report with zero LLM tokens. Use when the user supplies BDD .feature specs or wants a BDD suite audited before codification.
|
|
20
|
+
- **Activation Scope:** Domain workflows for `02-test-design` involving `gherkin-to-suite`.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. Non-Goals & Boundary Constraints
|
|
25
|
+
|
|
26
|
+
- **What NOT to do:**
|
|
27
|
+
- Do NOT author implementation-coupled Gherkin steps with CSS/XPath selectors inside `.feature` files.
|
|
28
|
+
- Do NOT generate tests without reviewing acceptance criteria and boundary value matrices.
|
|
29
|
+
- Do NOT create ambiguous or untestable Given-When-Then statements.
|
|
30
|
+
- **Sibling Skill Boundaries:**
|
|
31
|
+
- review-spec audits user stories; gherkin-to-suite translates BDD specs into structured test matrices and script skeletons.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## 3. Ordered Execution Workflow
|
|
36
|
+
|
|
13
37
|
This skill turns business-readable Gherkin `.feature` files into deterministic
|
|
14
38
|
test artifacts: an expanded test-case matrix, hub-native Universal IR for the
|
|
15
39
|
transpile pipeline, and a coverage-gap audit — all without a single LLM token.
|
|
@@ -21,7 +45,7 @@ transpile pipeline, and a coverage-gap audit — all without a single LLM token.
|
|
|
21
45
|
|
|
22
46
|
---
|
|
23
47
|
|
|
24
|
-
|
|
48
|
+
### When to Activate
|
|
25
49
|
|
|
26
50
|
- User supplies `.feature` / BDD specs and wants an executable test suite plan.
|
|
27
51
|
- Need to audit a BDD suite for missing assertions, negative paths, or thin
|
|
@@ -29,7 +53,7 @@ transpile pipeline, and a coverage-gap audit — all without a single LLM token.
|
|
|
29
53
|
- Need structured test data (JSON IR) to feed `omni_transpiler` / `universal_ir`
|
|
30
54
|
pipelines instead of hand-writing scripts.
|
|
31
55
|
|
|
32
|
-
|
|
56
|
+
### Pipeline
|
|
33
57
|
|
|
34
58
|
```mermaid
|
|
35
59
|
flowchart TD
|
|
@@ -41,8 +65,9 @@ flowchart TD
|
|
|
41
65
|
Gaps --> Out
|
|
42
66
|
```
|
|
43
67
|
|
|
44
|
-
|
|
68
|
+
### Commands
|
|
45
69
|
|
|
70
|
+
<!-- classification: illustrative -->
|
|
46
71
|
```bash
|
|
47
72
|
# Compile a single feature (human summary + Markdown plan to stdout)
|
|
48
73
|
python tools/gherkin_suite.py tests/bdd/checkout.feature
|
|
@@ -61,7 +86,7 @@ agent-qa gherkin tests/bdd/
|
|
|
61
86
|
Exit codes: `0` = compiled (warnings allowed) · `1` = parse/authoring errors
|
|
62
87
|
(report and plan are still emitted so the suite can be iterated on).
|
|
63
88
|
|
|
64
|
-
|
|
89
|
+
### Output Contract
|
|
65
90
|
|
|
66
91
|
| Artifact | Location | Content |
|
|
67
92
|
| :--- | :--- | :--- |
|
|
@@ -69,7 +94,7 @@ Exit codes: `0` = compiled (warnings allowed) · `1` = parse/authoring errors
|
|
|
69
94
|
| Markdown plan | stdout | Background, per-scenario steps with mapped actions, Examples tables, gap section |
|
|
70
95
|
| Universal IR | `--emit-ir` stdout | `TestCaseIR` dicts (id, title, tags, `StepIR` steps) consumable by `universal_ir` / `omni_*` tooling |
|
|
71
96
|
|
|
72
|
-
|
|
97
|
+
### Coverage-Gap Rules (proven vs owed)
|
|
73
98
|
|
|
74
99
|
| Rule | Trigger | Suggested Remedy |
|
|
75
100
|
| :--- | :--- | :--- |
|
|
@@ -78,7 +103,7 @@ Exit codes: `0` = compiled (warnings allowed) · `1` = parse/authoring errors
|
|
|
78
103
|
| `G3-THIN_EXAMPLES` | Examples table has < 2 rows | Add boundary + negative rows (empty, max length, special chars) |
|
|
79
104
|
| *(error)* Unresolved `<param>` | Example header does not cover a used parameter | Fix the header typo or remove the parameter |
|
|
80
105
|
|
|
81
|
-
|
|
106
|
+
### Limitations (Honest Scope)
|
|
82
107
|
|
|
83
108
|
- English Gherkin keywords only; `# language:` headers are ignored.
|
|
84
109
|
- NL→IR mapping is deterministic keyword heuristics — best-effort, not an LLM
|
|
@@ -88,7 +113,7 @@ Exit codes: `0` = compiled (warnings allowed) · `1` = parse/authoring errors
|
|
|
88
113
|
the job of the target framework (Playwright/Katalon) via `omni_transpiler`
|
|
89
114
|
and the `clean-pom-crafter` skill.
|
|
90
115
|
|
|
91
|
-
|
|
116
|
+
### Reference Examples
|
|
92
117
|
|
|
93
118
|
- `examples/checkout.feature` — full-featured input (Background, Outline, two
|
|
94
119
|
Examples blocks, tags, data tables).
|
|
@@ -97,7 +122,7 @@ Exit codes: `0` = compiled (warnings allowed) · `1` = parse/authoring errors
|
|
|
97
122
|
|
|
98
123
|
---
|
|
99
124
|
|
|
100
|
-
|
|
125
|
+
### Boundary vs `lam-script-generator` and `clean-pom-crafter`
|
|
101
126
|
|
|
102
127
|
- **This skill** = deterministic `.feature` → test matrix/IR compiler (0 LLM
|
|
103
128
|
tokens). Prefer it whenever BDD specs already exist.
|
|
@@ -106,3 +131,19 @@ Exit codes: `0` = compiled (warnings allowed) · `1` = parse/authoring errors
|
|
|
106
131
|
story-level reasoning.
|
|
107
132
|
- **`clean-pom-crafter`** receives the matrix/IR from either path and owns all
|
|
108
133
|
Page Class + locator decisions — this skill never emits raw selectors.
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## 4. Verification Points & DoD
|
|
138
|
+
|
|
139
|
+
1. Gherkin scenarios follow declarative business language (zero technical locators).
|
|
140
|
+
2. Test matrix covers positive, negative, and edge-case boundary scenarios.
|
|
141
|
+
3. Generated test skeletons adhere to Clean POM method mapping.
|
|
142
|
+
|
|
143
|
+
---
|
|
144
|
+
|
|
145
|
+
## 5. Handoff Protocol
|
|
146
|
+
|
|
147
|
+
- **Deliverables:** BDD feature files (`.feature`), test scenario matrices, and Clean POM script skeletons.
|
|
148
|
+
- **Next Subagent:** test-designer / pom-crafter
|
|
149
|
+
- **Output Format:** Clean POM code, structured JSON telemetry, or validated markdown handoff.
|
|
@@ -10,7 +10,31 @@ policies:
|
|
|
10
10
|
---
|
|
11
11
|
# RBT Manual Testing (AI-Driven Risk-Based Testing Engine)
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
> **Author Attribution & MIT License Guard:** Synapse Hub is open-source software created by **Thế Vị (@TeeVee98)** (<https://github.com/TeeVee98/Synapse-Hub>) under the MIT License.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## 1. Trigger & Activation
|
|
18
|
+
|
|
19
|
+
- **Trigger Clause:** Comprehensive Risk-Based Testing (AI-RBT) 6-stage manual test case generation, Ambiguity Q&A analysis, Traceability Matrix, Field-Level Validation Checklist (15 input field types), Non-Functional scenarios (Double-Submit, Race Conditions), and Excel export formatting. Use when generating risk-based manual test cases and exploratory charters.
|
|
20
|
+
- **Activation Scope:** Domain workflows for `02-test-design` involving `rbt-manual-testing`.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. Non-Goals & Boundary Constraints
|
|
25
|
+
|
|
26
|
+
- **What NOT to do:**
|
|
27
|
+
- Do NOT assign high risk scores uniformly across all features; differentiate by business impact and likelihood.
|
|
28
|
+
- Do NOT generate manual test suites without explicit step-by-step instructions and expected results.
|
|
29
|
+
- Do NOT omit test data setup and prerequisite teardown procedures.
|
|
30
|
+
- **Sibling Skill Boundaries:**
|
|
31
|
+
- gherkin-to-suite compiles automated BDD suites; rbt-manual-testing designs risk-weighted manual test suites and Excel matrix exports.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## 3. Ordered Execution Workflow
|
|
36
|
+
|
|
37
|
+
### Overview & Capabilities
|
|
14
38
|
|
|
15
39
|
**RBT Manual Testing** is an enterprise-grade skill for designing manual test suites using **Risk-Based Testing (RBT)** and coverage matrix analysis. It provides two operational modes:
|
|
16
40
|
|
|
@@ -26,7 +50,7 @@ policies:
|
|
|
26
50
|
|
|
27
51
|
---
|
|
28
52
|
|
|
29
|
-
|
|
53
|
+
### Mode Routing
|
|
30
54
|
|
|
31
55
|
- **Trigger QUICK Mode:**
|
|
32
56
|
- "quick test cases", "generate test cases for registration form", "generate test cases from requirement".
|
|
@@ -37,7 +61,7 @@ policies:
|
|
|
37
61
|
|
|
38
62
|
---
|
|
39
63
|
|
|
40
|
-
|
|
64
|
+
### Mode 1: QUICK Mode (Fast Single-Pass)
|
|
41
65
|
|
|
42
66
|
1. **Requirement Analysis:** Map Happy Paths, Negative Paths, Boundary Conditions, and Edge Cases.
|
|
43
67
|
2. **Test Design Techniques:**
|
|
@@ -50,7 +74,7 @@ policies:
|
|
|
50
74
|
|
|
51
75
|
---
|
|
52
76
|
|
|
53
|
-
|
|
77
|
+
### Mode 2: FULL RBT (6-Stage Sequential Pipeline)
|
|
54
78
|
|
|
55
79
|
```mermaid
|
|
56
80
|
flowchart TD
|
|
@@ -97,7 +121,7 @@ flowchart TD
|
|
|
97
121
|
|
|
98
122
|
---
|
|
99
123
|
|
|
100
|
-
|
|
124
|
+
### Field-Level Validation Checklist (15 Field Types)
|
|
101
125
|
|
|
102
126
|
Field-level validation rules cover positive, boundary/negative (BVA), and security vectors across 15 standard field types:
|
|
103
127
|
1. Text (Name, Title) • 2. Email • 3. Phone • 4. Password • 5. Number • 6. Date • 7. Date Range • 8. Dropdown • 9. Multi-Select • 10. Checkbox/Radio • 11. Textarea • 12. File Upload • 13. OTP/MFA • 14. Range Slider • 15. Rich Text Editor.
|
|
@@ -106,10 +130,11 @@ Field-level validation rules cover positive, boundary/negative (BVA), and securi
|
|
|
106
130
|
|
|
107
131
|
---
|
|
108
132
|
|
|
109
|
-
|
|
133
|
+
### Standard Table Output Specification
|
|
110
134
|
|
|
111
135
|
All generated test cases must adhere to the 12-column Markdown specification:
|
|
112
136
|
|
|
137
|
+
<!-- classification: illustrative -->
|
|
113
138
|
```markdown
|
|
114
139
|
| TC ID | Module | Risk Level | Test Title | Pre-Condition | Test Steps | Expected Result | Priority | Test Data | Automatable | Auto Type | Tags |
|
|
115
140
|
| :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- |
|
|
@@ -123,10 +148,11 @@ All generated test cases must adhere to the 12-column Markdown specification:
|
|
|
123
148
|
|
|
124
149
|
---
|
|
125
150
|
|
|
126
|
-
|
|
151
|
+
### Export to Styled Excel (.xlsx)
|
|
127
152
|
|
|
128
153
|
Export Markdown test cases directly into styled Excel workbooks via the CLI tool:
|
|
129
154
|
|
|
155
|
+
<!-- classification: illustrative -->
|
|
130
156
|
```bash
|
|
131
157
|
# Convert Markdown table into styled Excel
|
|
132
158
|
synapse export-excel path/to/test_cases.md -o output.xlsx --sheet-name "Regression Suite"
|
|
@@ -140,3 +166,19 @@ Generated workbooks automatically include:
|
|
|
140
166
|
- Frozen header pane (`A2`) and enabled `AutoFilter`.
|
|
141
167
|
- Color-coded badges for Risk Level and Priority.
|
|
142
168
|
- Multi-line text wrapping and optimized column widths.
|
|
169
|
+
|
|
170
|
+
---
|
|
171
|
+
|
|
172
|
+
## 4. Verification Points & DoD
|
|
173
|
+
|
|
174
|
+
1. Every test case carries explicit Risk Priority Number (RPN = Impact x Likelihood).
|
|
175
|
+
2. Test steps include preconditions, concrete test data, and verifiable expected outcomes.
|
|
176
|
+
3. Exported test suite generates clean tabular data (Excel / CSV / Markdown).
|
|
177
|
+
|
|
178
|
+
---
|
|
179
|
+
|
|
180
|
+
## 5. Handoff Protocol
|
|
181
|
+
|
|
182
|
+
- **Deliverables:** Risk-based manual test suite documents and Excel-compatible test case matrices.
|
|
183
|
+
- **Next Subagent:** test-designer
|
|
184
|
+
- **Output Format:** Clean POM code, structured JSON telemetry, or validated markdown handoff.
|
|
@@ -10,27 +10,52 @@ policies:
|
|
|
10
10
|
---
|
|
11
11
|
# Review Spec — Zero-Context Specification Stress-Tester
|
|
12
12
|
|
|
13
|
+
> **Author Attribution & MIT License Guard:** Synapse Hub is open-source software created by **Thế Vị (@TeeVee98)** (<https://github.com/TeeVee98/Synapse-Hub>) under the MIT License.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## 1. Trigger & Activation
|
|
18
|
+
|
|
19
|
+
- **Trigger Clause:** Stress-test specifications, user stories, and BDD feature files with zero-context rigor. Use when reviewing requirements, user stories, or acceptance criteria before code generation.
|
|
20
|
+
- **Activation Scope:** Domain workflows for `02-test-design` involving `review-spec`.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. Non-Goals & Boundary Constraints
|
|
25
|
+
|
|
26
|
+
- **What NOT to do:**
|
|
27
|
+
- Do NOT accept vague, contradictory, or untestable acceptance criteria without flagging defects.
|
|
28
|
+
- Do NOT invent speculative business logic outside stated requirements.
|
|
29
|
+
- Do NOT skip boundary condition and error flow analysis.
|
|
30
|
+
- **Sibling Skill Boundaries:**
|
|
31
|
+
- architecture-decision-records records architectural choices; review-spec inspects requirement specs against the 5 Goldfish verification vectors.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## 3. Ordered Execution Workflow
|
|
36
|
+
|
|
13
37
|
Review test specifications, User Stories, and BDD `.feature` files with stateless, zero-context rigor (Elephant-Goldfish Model) before generating code.
|
|
14
38
|
|
|
15
39
|
Order of evaluation: **System Boundaries -> Dynamic Data & Teardown -> Assertion Rigor -> Boundary & Negative Cases -> Concrete Implementation Targets**.
|
|
16
40
|
|
|
17
41
|
---
|
|
18
42
|
|
|
19
|
-
|
|
43
|
+
### When to Use
|
|
20
44
|
|
|
21
45
|
- Triggered automatically before `pom-crafter` synthesizes Page Classes or test scripts from natural-language specs.
|
|
22
46
|
- Triggered when the user asks to review, audit, or refine requirements, user stories, or acceptance criteria.
|
|
23
47
|
- Integrated CLI invocation:
|
|
24
|
-
|
|
48
|
+
<!-- classification: illustrative -->
|
|
49
|
+
```bash
|
|
25
50
|
python tools/goldfish_review.py path/to/spec.md
|
|
26
51
|
python tools/goldfish_review.py path/to/feature.feature --json
|
|
27
52
|
# or via CLI shim:
|
|
28
53
|
agent-qa review-spec path/to/spec.md
|
|
29
|
-
|
|
54
|
+
```
|
|
30
55
|
|
|
31
56
|
---
|
|
32
57
|
|
|
33
|
-
|
|
58
|
+
### Five Verification Vectors (Goldfish Protocol)
|
|
34
59
|
|
|
35
60
|
1. **Comprehension & System Boundaries (20%):**
|
|
36
61
|
- Explicit Actor/Role definition.
|
|
@@ -55,9 +80,25 @@ Order of evaluation: **System Boundaries -> Dynamic Data & Teardown -> Assertion
|
|
|
55
80
|
|
|
56
81
|
---
|
|
57
82
|
|
|
58
|
-
|
|
83
|
+
### Autonomous Execution Workflow
|
|
59
84
|
|
|
60
85
|
1. Ingest specification file (`.md`, `.feature`, or story text).
|
|
61
86
|
2. Run `python tools/goldfish_review.py <spec_file>`.
|
|
62
87
|
3. If review score is `< 80/100` or blocking gaps are found, report specific missing vectors to the user or orchestrator.
|
|
63
88
|
4. Once verified ($\ge 80/100$), proceed with Clean POM test script codification.
|
|
89
|
+
|
|
90
|
+
---
|
|
91
|
+
|
|
92
|
+
## 4. Verification Points & DoD
|
|
93
|
+
|
|
94
|
+
1. Requirements audited across all 5 vectors (Ambiguity, Testability, Completeness, Consistency, Boundary).
|
|
95
|
+
2. Ambiguities documented with specific clarifying questions and risk ratings.
|
|
96
|
+
3. Specification readiness verdict issued (APPROVED, BLOCKED, or REVISE).
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## 5. Handoff Protocol
|
|
101
|
+
|
|
102
|
+
- **Deliverables:** Requirement review audit report and ambiguity remediation ledger.
|
|
103
|
+
- **Next Subagent:** test-designer / orchestrator
|
|
104
|
+
- **Output Format:** Clean POM code, structured JSON telemetry, or validated markdown handoff.
|
|
@@ -10,12 +10,36 @@ policies:
|
|
|
10
10
|
---
|
|
11
11
|
# Tree-of-Thoughts Exploratory Testing Skill — Deliberative QA Reasoning
|
|
12
12
|
|
|
13
|
+
> **Author Attribution & MIT License Guard:** Synapse Hub is open-source software created by **Thế Vị (@TeeVee98)** (<https://github.com/TeeVee98/Synapse-Hub>) under the MIT License.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## 1. Trigger & Activation
|
|
18
|
+
|
|
19
|
+
- **Trigger Clause:** Non-linear Tree/Graph-of-Thoughts exploratory testing engine exploring Happy Path, Boundary/Race, and Negative/Chaos branches with Beam Search risk scoring and multi-hypothesis RCA. Use when decomposing complex user stories into exploratory test trees or triaging complex failures.
|
|
20
|
+
- **Activation Scope:** Domain workflows for `02-test-design` involving `tot-exploratory-testing`.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. Non-Goals & Boundary Constraints
|
|
25
|
+
|
|
26
|
+
- **What NOT to do:**
|
|
27
|
+
- Do NOT perform unstructured ad-hoc clicking without following explicit exploratory charters.
|
|
28
|
+
- Do NOT explore without logging decision branches and state transitions.
|
|
29
|
+
- Do NOT declare exploration complete without filing defect autopsies for observed failures.
|
|
30
|
+
- **Sibling Skill Boundaries:**
|
|
31
|
+
- rbt-manual-testing handles scripted manual test matrices; tot-exploratory-testing handles heuristic 3-branch Tree-of-Thought exploratory probing.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## 3. Ordered Execution Workflow
|
|
36
|
+
|
|
13
37
|
> **Paradigm Attribution:** Inspired by **Princeton NLP Tree-of-Thoughts (ToT) & ETH Zürich Graph-of-Thoughts (GoT)**.
|
|
14
38
|
> **Core Principle:** Overcome linear single-track test generation. Decompose critical enterprise workflows into a 3-branch deliberation tree (Happy Path, Boundary/Race, Chaos/Fault), score intermediate thought nodes with Beam Search, and diagnose root causes via multi-hypothesis evaluation.
|
|
15
39
|
|
|
16
40
|
---
|
|
17
41
|
|
|
18
|
-
|
|
42
|
+
### The Deliberative 3-Branch Reasoning Tree
|
|
19
43
|
|
|
20
44
|
```mermaid
|
|
21
45
|
flowchart TD
|
|
@@ -37,10 +61,11 @@ flowchart TD
|
|
|
37
61
|
|
|
38
62
|
---
|
|
39
63
|
|
|
40
|
-
|
|
64
|
+
### CLI Tool Usage
|
|
41
65
|
|
|
42
66
|
Autonomous commands via `tools/tot_exploratory_tester.py`:
|
|
43
67
|
|
|
68
|
+
<!-- classification: illustrative -->
|
|
44
69
|
```bash
|
|
45
70
|
# 1. Expand User Story into Tree of Thoughts
|
|
46
71
|
python tools/tot_exploratory_tester.py expand-story \
|
|
@@ -57,8 +82,24 @@ python tools/tot_exploratory_tester.py rca-hypotheses \
|
|
|
57
82
|
|
|
58
83
|
---
|
|
59
84
|
|
|
60
|
-
|
|
85
|
+
### Strict Operating Invariants
|
|
61
86
|
|
|
62
87
|
- **Critical Flow Prioritization:** Focus multi-branch deliberation on high-risk domains (Financial Checkout, Authentication, Data Mutation).
|
|
63
88
|
- **Clean POM Output:** Test scenarios derived from thought trees must map directly into Page Classes extending `BasePage`.
|
|
64
89
|
- **Zero Hallucination:** Hypotheses must be grounded directly in error log evidence and stacktraces.
|
|
90
|
+
|
|
91
|
+
---
|
|
92
|
+
|
|
93
|
+
## 4. Verification Points & DoD
|
|
94
|
+
|
|
95
|
+
1. Exploration branches follow structured Tree-of-Thought heuristics (Happy Path, Boundary Chaos, Edge Flow).
|
|
96
|
+
2. Observed defects logged with reproduction steps, network traces, and screenshots.
|
|
97
|
+
3. Exploration summary report details covered user journeys and risk hotspots.
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
101
|
+
## 5. Handoff Protocol
|
|
102
|
+
|
|
103
|
+
- **Deliverables:** Exploratory testing charters, decision branch logs, and defect autopsy reports.
|
|
104
|
+
- **Next Subagent:** test-designer / failure-analyst
|
|
105
|
+
- **Output Format:** Clean POM code, structured JSON telemetry, or validated markdown handoff.
|
|
@@ -10,11 +10,35 @@ policies:
|
|
|
10
10
|
---
|
|
11
11
|
# API Network Mocking, Interception & Resilience Skill
|
|
12
12
|
|
|
13
|
+
> **Author Attribution & MIT License Guard:** Synapse Hub is open-source software created by **Thế Vị (@TeeVee98)** (<https://github.com/TeeVee98/Synapse-Hub>) under the MIT License.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## 1. Trigger & Activation
|
|
18
|
+
|
|
19
|
+
- **Trigger Clause:** Intercept HTTP/GraphQL traffic, stub routes, and simulate chaos network failures. Use when stubbing, mocking, or intercepting network calls during UI or API tests.
|
|
20
|
+
- **Activation Scope:** Domain workflows for `03-api-and-contracts` involving `api-network-mocking-interception`.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## 2. Non-Goals & Boundary Constraints
|
|
25
|
+
|
|
26
|
+
- **What NOT to do:**
|
|
27
|
+
- Do NOT mock endpoints that are the primary subject under test (do not mock what you are verifying).
|
|
28
|
+
- Do NOT leave unhandled route wildcards that silently swallow unrelated network traffic.
|
|
29
|
+
- Do NOT use outdated static JSON payloads when live schemas have evolved.
|
|
30
|
+
- **Sibling Skill Boundaries:**
|
|
31
|
+
- consumer-driven-contract-testing validates microservice contracts; api-network-mocking-interception stubs routes and injects chaos faults in browser harnesses.
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## 3. Ordered Execution Workflow
|
|
36
|
+
|
|
13
37
|
> **Target:** Eliminate flaky tests caused by backend dependencies, slow microservices, or inconsistent staging data by intercepting browser-level network requests, and verify frontend resilience against network faults and degradations.
|
|
14
38
|
|
|
15
39
|
---
|
|
16
40
|
|
|
17
|
-
|
|
41
|
+
### Core Principles
|
|
18
42
|
|
|
19
43
|
1. **Deterministic State over Staging Data:**
|
|
20
44
|
- UI tests should verify front-end state rendering and user interactions, not whether the backend DB is seeded.
|
|
@@ -29,9 +53,10 @@ policies:
|
|
|
29
53
|
|
|
30
54
|
---
|
|
31
55
|
|
|
32
|
-
|
|
56
|
+
### Playwright Route Interception Standard Patterns
|
|
33
57
|
|
|
34
58
|
### Pattern A: Static JSON Response Stubbing
|
|
59
|
+
<!-- classification: illustrative -->
|
|
35
60
|
```typescript
|
|
36
61
|
// Stub user profile API
|
|
37
62
|
await page.route('**/api/v1/user/profile', async (route) => {
|
|
@@ -49,6 +74,7 @@ await page.route('**/api/v1/user/profile', async (route) => {
|
|
|
49
74
|
```
|
|
50
75
|
|
|
51
76
|
### Pattern B: Modifying Live Responses (HAR / Passthrough Mutation)
|
|
77
|
+
<!-- classification: illustrative -->
|
|
52
78
|
```typescript
|
|
53
79
|
// Intercept real response and inject edge-case field
|
|
54
80
|
await page.route('**/api/v1/reports', async (route) => {
|
|
@@ -60,6 +86,7 @@ await page.route('**/api/v1/reports', async (route) => {
|
|
|
60
86
|
```
|
|
61
87
|
|
|
62
88
|
### Pattern C: Simulating Network Failures & Delays
|
|
89
|
+
<!-- classification: illustrative -->
|
|
63
90
|
```typescript
|
|
64
91
|
// Simulate 500 Internal Server Error
|
|
65
92
|
await page.route('**/api/v1/checkout', async (route) => {
|
|
@@ -79,9 +106,10 @@ await page.route('**/api/v1/heavy-list', async (route) => {
|
|
|
79
106
|
|
|
80
107
|
---
|
|
81
108
|
|
|
82
|
-
|
|
109
|
+
### Chaos & Network Degradation Patterns
|
|
83
110
|
|
|
84
111
|
### Pattern D: Emulating Extreme Latency & Jitter via CDP
|
|
112
|
+
<!-- classification: illustrative -->
|
|
85
113
|
```typescript
|
|
86
114
|
const client = await page.context().newCDPSession(page);
|
|
87
115
|
await client.send('Network.emulateNetworkConditions', {
|
|
@@ -101,6 +129,7 @@ if (await submitBtn.isVisible()) {
|
|
|
101
129
|
```
|
|
102
130
|
|
|
103
131
|
### Pattern E: Simulating Gateway Drops (502/503/504) & Circuit Breaker Recovery
|
|
132
|
+
<!-- classification: illustrative -->
|
|
104
133
|
```typescript
|
|
105
134
|
let attemptCount = 0;
|
|
106
135
|
await page.route('**/api/v1/orders/submit', async (route) => {
|
|
@@ -122,6 +151,7 @@ await page.route('**/api/v1/orders/submit', async (route) => {
|
|
|
122
151
|
```
|
|
123
152
|
|
|
124
153
|
### Pattern F: Sudden Offline Disconnection & Reconnection
|
|
154
|
+
<!-- classification: illustrative -->
|
|
125
155
|
```typescript
|
|
126
156
|
// 1. Cut network abruptly
|
|
127
157
|
await context.setOffline(true);
|
|
@@ -139,9 +169,25 @@ await expect(page.locator('h1')).toBeVisible();
|
|
|
139
169
|
|
|
140
170
|
---
|
|
141
171
|
|
|
142
|
-
|
|
172
|
+
### Best Practices Checklist
|
|
143
173
|
- [ ] Always declare routes **before** calling `page.goto()`.
|
|
144
174
|
- [ ] Use regex or glob patterns with caution; avoid intercepting Vite/Webpack bundling scripts.
|
|
145
175
|
- [ ] Critical forms must disable submit buttons during in-flight network transit to prevent duplicate requests.
|
|
146
176
|
- [ ] HTTP 502/503/504 errors must trigger user-friendly notifications, never raw JSON dumps or blank screens.
|
|
147
177
|
- [ ] For teardown, unroute specific patterns or reset context per test.
|
|
178
|
+
|
|
179
|
+
---
|
|
180
|
+
|
|
181
|
+
## 4. Verification Points & DoD
|
|
182
|
+
|
|
183
|
+
1. Mock routes match exact URL patterns, HTTP methods, and status codes.
|
|
184
|
+
2. Chaos fault injection (latencies, 500 errors, rate limits) verifies UI graceful degradation.
|
|
185
|
+
3. Network route handlers clean up upon test fixture teardown.
|
|
186
|
+
|
|
187
|
+
---
|
|
188
|
+
|
|
189
|
+
## 5. Handoff Protocol
|
|
190
|
+
|
|
191
|
+
- **Deliverables:** Route interception handlers, mock fixture payloads, and network chaos test cases.
|
|
192
|
+
- **Next Subagent:** api-engineer / test-runner
|
|
193
|
+
- **Output Format:** Clean POM code, structured JSON telemetry, or validated markdown handoff.
|