Scopepath QA

Scopepath QA helps QA engineers and developers analyze change requests inside VS Code.

Website: scopepath-qa.lovable.app

It can start from a GitHub pull request, a Jira ticket, or a local spec/document and turn that input into:

• change context
• project profiling
• risk analysis
• test strategy
• automation recommendations

What Scopepath QA Is For

Use Scopepath QA when you want help answering questions like:

• What changed in this PR and what should we test?
• Does this Jira ticket already imply a test plan?
• What test cases are missing?
• What should be automated at unit, API, UI, or performance level?
• Which framework fits this project best based on the current stack?
• Should this team stay on Playwright, Cypress, Selenium, Robot Framework, k6, JMeter, or BlazeMeter?

Main Workflows

PR + Jira Analysis

Use this when you have a GitHub PR and a related Jira ticket.

Scopepath QA can:

• inspect the PR
• connect the technical diff with business context
• identify risks and coverage gaps
• suggest the right test scope
• recommend automation to add or update
• align recommendations to the framework the repo already uses

Jira-Only Analysis

Use this when work starts from a ticket instead of a PR.

Scopepath QA can:

• read the ticket context
• infer whether a test plan is needed
• outline the test plan structure
• suggest manual and automated coverage
• recommend the right framework for future automation

Spec-Driven Analysis

Use this when the change starts from a spec or local documentation.

Scopepath QA can:

• read project docs or feature specs
• extract business rules and acceptance criteria
• map expected testing needs before implementation exists
• suggest the most compatible framework based on repository evidence

Commands

After installation, open the Command Palette and run:

• Scopepath QA: Run Setup & Health Check
• Scopepath QA: Connect GitHub
• Scopepath QA: Connect Jira
• Scopepath QA: Set Up Current Project
• Scopepath QA: Analyze Change
• Scopepath QA: Analyze Jira Work Item

Recommended Setup

1. Install the extension.
2. Run Scopepath QA: Run Setup & Health Check.
3. Create your GitHub and Jira connection profiles.
4. Set up each workspace folder with Scopepath QA: Set Up Current Project.
5. Start with either Scopepath QA: Analyze Change or Scopepath QA: Analyze Jira Work Item.

Publishing Notes

Scopepath QA is designed for teams working across multiple repositories, frameworks, and delivery styles.

It can support workflows that start from:

• a GitHub pull request
• a Jira ticket
• a feature specification
• local project documentation

What Scopepath QA Needs

Required

• VS Code 1.105 or newer
• GitHub Copilot Chat with agent support

Recommended

• GitHub CLI authenticated if you work with GitHub PRs
• Atlassian access if you work with Jira or Confluence
• Node.js and Python for some local tooling and MCP helpers

Framework Awareness

Scopepath QA can profile and plan around teams using frameworks such as:

• Playwright
• Cypress
• Selenium
• Robot Framework
• pytest
• k6
• JMeter
• BlazeMeter

Scopepath QA should prefer the framework already established in the repository or specified in .masq/project.yml instead of introducing a new one without a good reason.

Multi-Project Support

Scopepath QA supports multi-root workspaces.

That means you can open multiple projects in the same VS Code window and keep different Scopepath QA project settings per folder through .masq/project.yml.

Security And Privacy

Scopepath QA can prompt for GitHub and Jira credentials to create reusable connection profiles.

• credentials are intended to stay local to your VS Code environment
• telemetry is anonymous and can be declined in VS Code
• project requests and generated artifacts are written into .masq/ inside the active workspace

Privacy, support, and license documents are included with the extension package.

Support

If you need help with Scopepath QA, use the support guidance included with the extension package.

You can also learn more about the product at scopepath-qa.lovable.app.

Goal

The goal of Scopepath QA is not just to generate tests.

Its real value is helping teams understand change faster, choose the right level of testing, and adapt automation strategy to different stacks, companies, and delivery processes.