qa-skills 3.0.0

package/skills/qa-jira-integration/SKILL.md

@@ -0,0 +1,135 @@
+---
+name: qa-jira-integration
+description: Jira integration for creating issues, managing epics/sprints, syncing with Xray/Zephyr test management, and tracking QA workflows via REST API or Atlassian MCP.
+dependencies:
+  recommended:
+    - qa-bug-ticket-creator
+    - qa-task-creator
+---
+
+# QA Jira Integration
+
+## Purpose
+
+Integrate QA workflow with Jira for issue tracking and project management. Create and update issues, manage epics and sprints, link issues to requirements and test cases, and sync with Xray/Zephyr for test management. Use Jira REST API or Atlassian MCP when available.
+
+## Features
+
+| Feature | Description |
+| ------- | ----------- |
+| **Create/update issues** | Bug, Story, Task, Sub-task with full field mapping |
+| **Manage epics and sprints** | Create epics, add issues to sprints, manage backlog |
+| **Link issues** | Link to requirements, test cases, parent issues |
+| **Xray/Zephyr integration** | Sync test cases, test executions, traceability |
+| **JQL queries** | Search and report on issues by project, status, assignee |
+| **Transition management** | Move issues through workflow states (To Do → In Progress → Done) |
+
+## Authentication
+
+| Variable | Description |
+| -------- | ----------- |
+| `JIRA_BASE_URL` | Jira instance URL (e.g., `https://your-domain.atlassian.net`) |
+| `JIRA_API_TOKEN` | API token from [Atlassian account settings](https://id.atlassian.com/manage-profile/security/api-tokens) |
+| `JIRA_EMAIL` | Email for the Atlassian account (used with API token) |
+
+**Basic Auth:** `Authorization: Basic base64(email:api_token)`
+
+See `references/api-patterns.md` for request examples.
+
+## Key API Patterns
+
+| Operation | Method | Endpoint |
+| --------- | ------ | -------- |
+| Create issue | POST | `/rest/api/3/issue` |
+| Search (JQL) | GET | `/rest/api/3/search?jql=...` |
+| Get issue | GET | `/rest/api/3/issue/{key}` |
+| Update issue | PUT | `/rest/api/3/issue/{key}` |
+| Transition | POST | `/rest/api/3/issue/{key}/transitions` |
+| Link issues | POST | `/rest/api/3/issueLink` |
+| Add comment | POST | `/rest/api/3/issue/{key}/comment` |
+| Add attachment | POST | `/rest/api/3/issue/{key}/attachments` |
+
+## Integration with qa-bug-ticket-creator
+
+When qa-bug-ticket-creator produces a bug report:
+
+1. **Map fields** — Use `references/field-mapping.md` to map bug report fields to Jira issue fields
+2. **Create Jira Bug** — POST to `/rest/api/3/issue` with `issuetype: { name: "Bug" }`
+3. **Link to test** — If test case key exists, create issue link (e.g., "tests" or "blocks")
+4. **Optional** — Invoke qa-task-creator for linked fix task; create as Jira Task/Sub-task under same project
+
+## Integration with qa-task-creator
+
+When qa-task-creator produces a task:
+
+1. **Map fields** — Map task type to Jira issuetype (Story, Task, Sub-task)
+2. **Create Jira issue** — POST with appropriate project key and issuetype
+3. **Link to parent** — If task references a bug, use `parent` for Sub-task or issue link for Task
+4. **Sprint assignment** — Add to sprint via `fields.customfield_XXXX` (sprint field ID varies by instance)
+
+## Trigger Phrases
+
+- "Create Jira issue from [bug report / task]"
+- "File bug in Jira for [test failure]"
+- "Add issue to sprint [name]"
+- "Search Jira for [JQL]"
+- "Transition [PROJ-123] to In Progress"
+- "Link [PROJ-123] to test case [PROJ-456]"
+- "Sync test results to Xray"
+
+## Workflow
+
+1. **Auth** — Load `JIRA_BASE_URL`, `JIRA_EMAIL`, `JIRA_API_TOKEN` from `.env`
+2. **Map** — Use `references/field-mapping.md` for QA → Jira field mapping
+3. **Create/Update** — Call REST API or Atlassian MCP
+4. **Link** — Create issue links, add to epic/sprint as needed
+5. **Report** — Use JQL for dashboards and status reports
+
+## Scope
+
+**Can do (autonomous):**
+- Create Bug, Story, Task, Sub-task via REST API
+- Search issues with JQL
+- Transition issues through workflow
+- Link issues (parent-child, blocks, relates to)
+- Add comments and attachments
+- Map QA bug/task output to Jira fields per `references/field-mapping.md`
+- Integrate with qa-bug-ticket-creator and qa-task-creator for issue creation
+
+**Cannot do (requires confirmation):**
+- Create issues in projects without configured access
+- Override user-specified assignee or sprint
+- Delete or bulk-modify issues
+
+**Will not do (out of scope):**
+- Modify Jira project configuration or workflows
+- Create custom fields (admin-only)
+- Execute tests or modify application code
+
+## Quality Checklist
+
+- [ ] Auth uses env vars; no hardcoded credentials
+- [ ] Field mapping follows `references/field-mapping.md`
+- [ ] Issue types and project keys validated before create
+- [ ] JQL queries are safe (no injection; use parameterization where supported)
+- [ ] Links to qa-bug-ticket-creator / qa-task-creator output preserved
+- [ ] Xray/Zephyr operations follow `references/xray-integration.md` when used
+
+## Troubleshooting
+
+| Symptom | Likely Cause | Fix |
+| ------- | ------------ | --- |
+| 401 Unauthorized | Invalid token or email | Regenerate API token; verify JIRA_EMAIL matches token owner |
+| 404 on create | Wrong project key or endpoint | Verify JIRA_BASE_URL; check project key exists |
+| 400 Bad Request | Invalid field value | Check `references/field-mapping.md`; verify custom field IDs |
+| Transition fails | Invalid transition ID | GET `/rest/api/3/issue/{key}/transitions` to list valid transitions |
+| Xray sync fails | Xray not installed or wrong project | Verify Xray app; use Xray-specific endpoints per `references/xray-integration.md` |
+| Field not found | Custom field ID wrong | Use GET `/rest/api/3/field` to list field IDs |
+
+## Reference Files
+
+| Topic | File |
+| ----- | ---- |
+| Jira REST API patterns | `references/api-patterns.md` |
+| QA → Jira field mapping | `references/field-mapping.md` |
+| Xray/Zephyr integration | `references/xray-integration.md` |

package/skills/qa-jira-integration/references/api-patterns.md

@@ -0,0 +1,143 @@
+# Jira REST API Patterns
+
+*Request/response patterns for common Jira REST API v3 operations.*
+
+---
+
+## Base URL
+
+```
+{JIRA_BASE_URL}/rest/api/3
+```
+
+Headers:
+```
+Authorization: Basic {base64(email:api_token)}
+Content-Type: application/json
+Accept: application/json
+```
+
+---
+
+## Create Issue
+
+**POST** `/rest/api/3/issue`
+
+```json
+{
+  "fields": {
+    "project": { "key": "PROJ" },
+    "summary": "Login fails when password contains special chars",
+    "description": {
+      "type": "doc",
+      "version": 1,
+      "content": [{
+        "type": "paragraph",
+        "content": [{ "type": "text", "text": "Expected: ... Actual: ..." }]
+      }]
+    },
+    "issuetype": { "name": "Bug" },
+    "priority": { "name": "High" },
+    "labels": ["auth", "frontend"],
+    "components": [{ "name": "Authentication" }]
+  }
+}
+```
+
+Response: `201 Created` with `{"key": "PROJ-123", "id": "12345"}`
+
+---
+
+## Search (JQL)
+
+**GET** `/rest/api/3/search?jql={jql}&maxResults=50&startAt=0`
+
+Example JQL:
+- `project = PROJ AND issuetype = Bug AND status != Done`
+- `sprint in openSprints() AND assignee = currentUser()`
+- `key = PROJ-123`
+
+Response: `{"issues": [...], "total": N}`
+
+---
+
+## Transition
+
+**GET** `/rest/api/3/issue/{key}/transitions` — List available transitions
+
+**POST** `/rest/api/3/issue/{key}/transitions`
+
+```json
+{
+  "transition": { "id": "31" }
+}
+```
+
+Transition IDs vary by workflow; fetch via GET first.
+
+---
+
+## Add Comment
+
+**POST** `/rest/api/3/issue/{key}/comment`
+
+```json
+{
+  "body": {
+    "type": "doc",
+    "version": 1,
+    "content": [{
+      "type": "paragraph",
+      "content": [{ "type": "text", "text": "Comment text" }]
+    }]
+  }
+}
+```
+
+---
+
+## Link Issues
+
+**POST** `/rest/api/3/issueLink`
+
+```json
+{
+  "type": { "name": "Blocks" },
+  "inwardIssue": { "key": "PROJ-123" },
+  "outwardIssue": { "key": "PROJ-124" }
+}
+```
+
+Link types: `Blocks`, `Cloners`, `Duplicate`, `Relates`, etc.
+
+---
+
+## Attach File
+
+**POST** `/rest/api/3/issue/{key}/attachments`
+
+`Content-Type: multipart/form-data` with file part.
+
+---
+
+## Sub-task (Parent)
+
+Add `"parent": { "key": "PROJ-100" }` to create sub-task under parent.
+
+---
+
+## Epic Link
+
+For classic projects: `"customfield_10014": "PROJ-50"` (field ID varies)
+
+For next-gen: Use `parent` or project-specific epic link field.
+
+---
+
+## Add to Sprint
+
+**POST** `/rest/api/3/sprint/{sprintId}/issue`
+
+Body: `{"issues": ["PROJ-123", "PROJ-124"]}`
+
+Or set `customfield_10020` (Sprint field ID varies) on issue create/update.

package/skills/qa-jira-integration/references/field-mapping.md

@@ -0,0 +1,79 @@
+# QA to Jira Field Mapping
+
+*Mapping local QA fields (from qa-bug-ticket-creator, qa-task-creator) to Jira fields.*
+
+---
+
+## Bug Report → Jira Bug
+
+| QA Bug Field | Jira Field | Jira API Path |
+| ------------ | ---------- | ------------- |
+| Title | Summary | `fields.summary` |
+| Expected Result + Actual Result + Steps | Description | `fields.description` (Atlassian Document Format) |
+| Severity | Priority | `fields.priority.name` |
+| Component/Module | Labels | `fields.labels[]` |
+| Component/Module | Components | `fields.components[].name` |
+| Environment | Description (append) or custom | Custom field or description |
+| Evidence | Attachments / Comment | Attach via `/attachments`; or embed in description |
+| Priority (P1–P5) | Priority or custom | Map P1→Highest, P2→High, etc. |
+
+---
+
+## Task → Jira Story/Task
+
+| QA Task Field | Jira Field | Jira API Path |
+| ------------- | ---------- | ------------- |
+| Title | Summary | `fields.summary` |
+| Description + Acceptance criteria | Description | `fields.description` |
+| Task type | Issue type | `fields.issuetype` (Story, Task) |
+| Labels | Labels | `fields.labels[]` |
+| Parent bug | Link or parent | `issueLink` or `fields.parent` |
+| Component | Components | `fields.components[].name` |
+
+---
+
+## Severity → Priority
+
+| QA Severity | Jira Priority |
+| ----------- | ------------- |
+| Blocker | Highest |
+| Critical | High |
+| Major | High / Medium |
+| Minor | Medium / Low |
+| Trivial | Low |
+
+---
+
+## Atlassian Document Format (ADF)
+
+Description and comments use ADF:
+
+```json
+{
+  "type": "doc",
+  "version": 1,
+  "content": [
+    {
+      "type": "heading",
+      "attrs": { "level": 3 },
+      "content": [{ "type": "text", "text": "Expected Result" }]
+    },
+    {
+      "type": "paragraph",
+      "content": [{ "type": "text", "text": "User should be able to log in." }]
+    }
+  ]
+}
+```
+
+For simple text, use a single paragraph node.
+
+---
+
+## Custom Fields
+
+Project-specific custom fields have IDs like `customfield_10001`. Use:
+
+**GET** `/rest/api/3/field` — List all fields and IDs.
+
+Map QA concepts (e.g., Fix Version, Sprint) to the correct custom field ID for the project.

package/skills/qa-jira-integration/references/xray-integration.md

@@ -0,0 +1,85 @@
+# Xray / Zephyr Test Management Integration
+
+*Patterns for syncing test cases and execution with Jira via Xray or Zephyr.*
+
+---
+
+## Xray (Xray for Jira)
+
+### Test Case as Jira Issue
+
+- **Issue type:** `Test` (or project-specific)
+- **Link types:** Test → Requirement (traceability)
+- **Custom fields:** Steps, Preconditions, Expected Result
+
+### REST API Endpoints (Xray)
+
+| Operation | Endpoint |
+| --------- | -------- |
+| Create test | `POST /rest/raven/2.0/api/test` |
+| Link test to requirement | `POST /rest/raven/2.0/api/test/{key}/requirement` |
+| Create test execution | `POST /rest/raven/2.0/api/testexec/{execKey}/test` |
+| Import test results (Xray format) | `POST /rest/raven/2.0/api/import/execution` |
+
+### Import Execution (Cucumber, JUnit, etc.)
+
+Xray accepts JUnit XML, Cucumber JSON, and other formats. POST to import endpoint with execution results; Xray creates/updates Test Execution and links to tests.
+
+---
+
+## Zephyr (Zephyr Scale / Squad)
+
+### Test Case as Jira Issue
+
+- **Issue type:** `Test` (Zephyr Scale)
+- **Traceability:** Test ↔ Requirement via Zephyr links
+
+### REST API (Zephyr Scale)
+
+| Operation | Endpoint |
+| --------- | -------- |
+| Create test | Zephyr Scale REST API (varies by version) |
+| Add to test cycle | Cycle and folder APIs |
+| Record execution | Execution API |
+
+Check Zephyr documentation for exact endpoints; they differ between Zephyr for Jira (classic) and Zephyr Scale.
+
+---
+
+## Common Patterns
+
+### 1. Link Test to Requirement
+
+After creating a Test issue in Jira:
+- **Xray:** Use Xray REST to link test key to requirement key
+- **Zephyr:** Use Zephyr API for traceability
+
+### 2. Import Automated Results
+
+1. Run tests (Playwright, pytest, Jest, etc.)
+2. Export results as JUnit XML or Cucumber JSON
+3. POST to Xray/Zephyr import endpoint
+4. Map test case IDs (e.g., `PROJ-T123`) to automated test names via mapping or naming convention
+
+### 3. Naming Convention
+
+Use consistent naming: `PROJ-T001`, `PROJ-T002` or map `describe/it` or `test_` names to test keys via a mapping file.
+
+---
+
+## Environment Variables
+
+| Variable | Description |
+| -------- | ----------- |
+| `JIRA_BASE_URL` | Same as main Jira |
+| `JIRA_API_TOKEN` | Same as main Jira |
+| `XRAY_CLIENT_ID` / `XRAY_CLIENT_SECRET` | For Xray Cloud API (if using OAuth) |
+
+---
+
+## Scope
+
+- Create Test issues and link to requirements
+- Import execution results from CI
+- Query test coverage per requirement
+- Sync with qa-test-reporter output (JUnit XML)

package/skills/qa-jmeter-writer/SKILL.md

@@ -0,0 +1,171 @@
+---
+name: qa-jmeter-writer
+description: Generate JMeter performance test plans in XML/JMX format with thread groups, samplers, listeners, assertions, and CI-ready configuration.
+output_dir: tests/performance
+---
+
+# QA JMeter Writer
+
+## Purpose
+
+Write JMeter test plans (.jmx) from performance test specifications. Transform structured performance requirements (from qa-plan-creator performance plans, qa-nfr-analyst NFR specs) into executable JMeter XML test plans with thread groups, samplers, listeners, assertions, and CI-ready configuration.
+
+## Trigger Phrases
+
+- "Write JMeter tests for [API/endpoint]"
+- "Generate JMeter load tests from performance plan"
+- "Create JMeter .jmx for [service]"
+- "JMeter thread group with HTTP samplers"
+- "JMeter test plan with assertions and listeners"
+- "JMeter CSV data parameterization"
+- "JMeter CI integration non-GUI mode"
+- "JMeter distributed load test plan"
+- "JMeter JSON assertion for API"
+- "JMeter JSR223 Groovy preprocessor"
+
+## Key Features
+
+| Feature | Description |
+|---------|-------------|
+| **Thread Groups** | Users, ramp-up, loops, duration for load modeling |
+| **HTTP Request Sampler** | URL, method, body, headers, path |
+| **JDBC/JMS Samplers** | Database and messaging protocol support |
+| **Listeners** | Aggregate Report, Summary Report, Graph Results, View Results Tree |
+| **Assertions** | Response Assertion, Duration Assertion, Size Assertion, JSON Assertion |
+| **CSV Data Set Config** | Parameterization from CSV files |
+| **Extractors** | Regular Expression Extractor, JSON Extractor |
+| **Timers** | Constant, Uniform Random, Gaussian for think time |
+| **Pre/Post Processors** | JSR223 (Groovy), BeanShell for correlation |
+
+## Workflow
+
+1. **Read performance plan** — From qa-plan-creator (performance plan) or qa-nfr-analyst (NFR specs)
+2. **Design thread groups** — Map load profiles to Thread Group (users, ramp-up, loops, duration)
+3. **Add samplers** — HTTP Request, JDBC, JMS as needed
+4. **Configure assertions** — Response, Duration, Size, JSON for validation
+5. **Add listeners** — Aggregate Report, Summary Report for results
+6. **Generate .jmx** — Produce valid JMeter XML test plan file
+
+## Key Patterns
+
+| Pattern | Usage |
+|---------|-------|
+| **Thread Group** | `num_threads`, `ramp_time`, `loops`, `duration` for load modeling |
+| **HTTP Request** | Domain, path, method, body, headers |
+| **Response Assertion** | Status code, response text, response code |
+| **Duration Assertion** | Max response time (ms) |
+| **JSON Assertion** | JSONPath, expected value |
+| **CSV Data Set Config** | Filename, variable names, delimiter |
+| **Regular Expression Extractor** | Regex, template, match number, variable |
+| **JSR223 PreProcessor** | Groovy script for correlation |
+
+### Thread Group Example
+
+```xml
+<ThreadGroup guiclass="ThreadGroupGui" testclass="ThreadGroup" testname="Load Users" enabled="true">
+  <stringProp name="ThreadGroup.num_threads">50</stringProp>
+  <stringProp name="ThreadGroup.ramp_time">60</stringProp>
+  <elementProp name="ThreadGroup.main_controller" elementType="LoopController">
+    <stringProp name="LoopController.loops">-1</stringProp>
+    <stringProp name="ThreadGroup.duration">300</stringProp>
+  </elementProp>
+</ThreadGroup>
+```
+
+### HTTP Request Sampler
+
+```xml
+<HTTPSamplerProxy guiclass="HttpTestSampleGui" testclass="HTTPSamplerProxy" testname="GET /api/users" enabled="true">
+  <stringProp name="HTTPSampler.domain">api.example.com</stringProp>
+  <stringProp name="HTTPSampler.path">/api/users</stringProp>
+  <stringProp name="HTTPSampler.method">GET</stringProp>
+  <boolProp name="HTTPSampler.use_keepalive">true</boolProp>
+</HTTPSamplerProxy>
+```
+
+### Response Assertion
+
+```xml
+<ResponseAssertion guiclass="AssertionGui" testclass="ResponseAssertion" testname="Status 200" enabled="true">
+  <collectionProp name="Assertion.test_strings">
+    <stringProp name="49586">200</stringProp>
+  </collectionProp>
+  <stringProp name="Assertion.custom_message"></stringProp>
+  <stringProp name="Assertion.test_field">Assertion.response_code</stringProp>
+  <boolProp name="Assertion.assume_success">false</boolProp>
+</ResponseAssertion>
+```
+
+See `references/patterns.md` for thread groups, samplers, assertions, extractors, timers, controllers.
+
+## Output
+
+- **JMeter test plans** — `.jmx` files in `tests/`, `performance/`, or `jmeter/` per project convention
+- **Run via CLI** — `jmeter -n -t test.jmx -l results.jtl -e -o report/`
+- **CI integration** — Non-GUI mode (`-n`), JTL results (`-l`), HTML report (`-e -o`)
+
+## CI Integration
+
+| Option | Description |
+|--------|-------------|
+| `-n` | Non-GUI mode (headless) |
+| `-t test.jmx` | Test plan file |
+| `-l results.jtl` | Results file (JTL/CSV) |
+| `-e` | Generate HTML report after run |
+| `-o report/` | Output directory for HTML report |
+| `-Jprop=value` | Override JMeter properties |
+
+## Scope
+
+**Can do (autonomous):**
+- Generate .jmx test plans from performance plans and NFR specs
+- Design thread groups (users, ramp-up, loops, duration)
+- Add HTTP, JDBC, JMS samplers with proper configuration
+- Configure Response, Duration, Size, JSON assertions
+- Add CSV Data Set Config for parameterization
+- Add Regular Expression Extractor, JSON Extractor for correlation
+- Add timers (Constant, Uniform Random) for think time
+- Add JSR223 PreProcessor (Groovy) for dynamic logic
+- Add listeners (Aggregate Report, Summary Report)
+- Generate CI-ready run commands
+
+**Cannot do (requires confirmation):**
+- Change production service configuration
+- Target production without explicit consent
+- Add JMeter plugins not in standard distribution
+- Override project JMeter config without approval
+
+**Will not do (out of scope):**
+- Execute tests (user runs `jmeter -n -t test.jmx`)
+- Write E2E functional tests (use qa-playwright-ts-writer)
+- Provision load infrastructure (distributed JMeter setup)
+- Modify CI/CD pipelines beyond JMeter integration
+
+## References
+
+- `references/patterns.md` — Thread groups, samplers, assertions, extractors, timers, controllers
+- `references/config.md` — CLI mode, properties, plugins, distributed testing
+- `references/best-practices.md` — Non-GUI mode, parameterization, correlation, result analysis
+
+## Quality Checklist
+
+- [ ] Thread groups match performance plan load profiles (users, ramp-up, duration)
+- [ ] Assertions validate critical responses (status, duration, size)
+- [ ] No hardcoded secrets; use `${__P()}` or CSV for credentials
+- [ ] Think time (timers) between requests where realistic
+- [ ] Listeners suitable for CI (Aggregate Report, Summary Report; avoid View Results Tree in load runs)
+- [ ] CSV Data Set Config for parameterization when needed
+- [ ] Extractors for correlation when session/token required
+- [ ] Test plan runs in non-GUI mode without errors
+
+## Troubleshooting
+
+| Symptom | Likely Cause | Fix |
+|---------|--------------|-----|
+| OutOfMemoryError in JMeter | Too many threads or listeners | Reduce threads; remove View Results Tree; increase JVM heap (`-Xmx`) |
+| Assertions fail in CI | Different baseline or env | Align assertion thresholds; use `${__P()}` for env-specific values |
+| High error rate | Timeouts, 5xx, or wrong assertions | Increase timeout; fix assertion logic; verify endpoint |
+| CSV not found | Relative path | Use absolute path or `${__BeanShell(import org.apache.jmeter.services.FileServer; FileServer.getFileServer().getBaseDir();)}` |
+| Correlation fails | Extractor order or regex | Ensure extractor runs before dependent sampler; verify regex |
+| JMX invalid XML | Malformed elements | Validate XML; ensure proper closing tags; check JMeter version compatibility |
+| Slow HTML report | Large JTL file | Use Aggregate Report listener; reduce sample logging; filter by label |