Enhancement: Modular QA Platform Architecture#1
Open
philmcneely wants to merge 3 commits into
Open
Conversation
Defines 10 independent modules covering the full testing lifecycle: requirements analysis, test design, case management, code generation, execution, self-healing, defect management, observability, visual regression, and API testing. Each module supports pluggable integration adapters (Jira, Azure DevOps, Linear, TestRail, etc.) so teams aren't locked to any single tool. Includes two example compositions (Jira+Zephyr and no-tools), implementation phases, and Zephyr testing strategy.
There was a problem hiding this comment.
Pull request overview
Adds a new enhancement/design document describing a modular QA platform architecture and an example end-to-end Jira + Zephyr workflow, intended to extend test-forge’s existing “front half” capabilities into a full testing lifecycle roadmap.
Changes:
- Introduces a 10-module conceptual architecture spanning requirements → design → execution → reporting.
- Documents example workflow compositions (Jira+Zephyr enterprise flow and a local/no-tools flow).
- Captures a proposed Zephyr Scale testing strategy and phased implementation plan.
Comments suppressed due to low confidence (2)
ENHANCEMENT-jira-zephyr-e2e-workflow.md:560
- This Zephyr env var list (
ZEPHYR_ENABLED,ZEPHYR_PROJECT_KEY,ZEPHYR_DRY_RUN) doesn’t appear elsewhere in this repo (current Zephyr integration is gated by--createplus presence ofZEPHYR_API_TOKEN, with optionalZEPHYR_BASE_URL). Please either align this list with the repo’s current configuration knobs or mark these as future/planned variables.
| `ZEPHYR_ENABLED` | `false` | TCM |
| `ZEPHYR_API_TOKEN` | — | TCM |
| `ZEPHYR_BASE_URL` | `https://api.zephyrscale.smartbear.com/v2` | TCM |
| `ZEPHYR_PROJECT_KEY` | — | TCM |
| `ZEPHYR_DRY_RUN` | `false` | TCM |
ENHANCEMENT-jira-zephyr-e2e-workflow.md:156
- Endpoints like
POST /testcyclesand the/testexecutionscreate/update calls aren’t referenced in this repo’s current Zephyr implementation (which only creates test cases). If these are intended for the Playwright frameworks’ future reporting module, consider moving them to a “planned endpoints” list to avoid overstating current support.
| `POST /testcycles` | Create test cycle |
| `POST /testexecutions` | Create test execution |
| `PUT /testexecutions/{id}` | Update execution status |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+148
to
+153
| **Zephyr Scale API endpoints used:** | ||
|
|
||
| | Endpoint | Purpose | | ||
| |---|---| | ||
| | `POST /testcases` | Create test case | | ||
| | `GET /testcases` | Duplicate detection | |
Comment on lines
+42
to
+46
| | AC Quality | Action | | ||
| |---|---| | ||
| | Structured + specific + edge cases | Proceed to test design | | ||
| | Structured but missing edge cases | Comment with suggestions, proceed with caveats | | ||
| | Vague or freeform | Comment with BDD rewrite suggestion, flag for author | |
Comment on lines
+543
to
+547
| | `JIRA_ENABLED` | `false` | TCM, Defect Mgmt | | ||
| | `JIRA_BASE` | — | All Jira modules | | ||
| | `JIRA_USER` | — | All Jira modules | | ||
| | `JIRA_TOKEN` | — | All Jira modules | | ||
| | `JIRA_JQL` | — | Requirements Analysis, Code Gen | |
Adds 12 modules (up from 10): exploratory testing and mobile testing. Defines Node.js/Fastify server with BullMQ job queue as the always-on runtime. Adds OpenAPI-based API contract testing, visual baseline grouping for mobile, cross-platform self-healing via view hierarchy, and 7-phase implementation roadmap.
…on, CI integration Expands platform from 12 to 17 modules. Adds consumer-driven contract testing (Pact), test data management with factories and PII masking, OWASP Top 10 security scanning (ZAP + dependency audit), database validation for post-operation verification, and CI-agnostic runner with templates for Jenkins/GitLab/CircleCI/Azure/TeamCity. Updates implementation roadmap from 7 to 9 phases. Adds env vars for all new modules.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
test-forge already has the front half built (confluence-clarify, confluence-breakdown, jira-clarify, jira-test-gen). This enhancement maps the full lifecycle and the modular architecture needed to support teams with different toolchains.
Test plan
--createpaths in jira skills work against Atlassian dev instance