[!IMPORTANT] Internal Tool Notice: This extension is built for Emerson employees. An active connection to the Emerson corporate network and valid Microsoft Entra ID access to Emerson's Azure DevOps organization are required.

A VS Code extension that integrates GitHub Copilot with Azure DevOps and Playwright to automatically generate and maintain Playwright test suites directly from Azure DevOps Test Cases and Work Items.

Central Repository & Collaboration

Agent prompt rules and Playwright framework templates are fetched dynamically at runtime from the centralized Azure DevOps repository:
👉 qcs-playwright-agent Repository

Administered by the QCS Team, but open to all Emerson employees for collaboration, updates, and contributions.
Custom Branch Support: Any user or team can create their own branch in the repository to experiment with custom prompts or framework templates.
Switch Branches in VS Code: Use the command QCS Playwright Automation: Switch Agent Branch to point your extension to any custom branch.

Prerequisites

Before using the extension, ensure you have:

Corporate Network & Account: Active connection to the Emerson network and a signed-in Microsoft account with access to Emerson's Azure DevOps organization.
VS Code: Version 1.96.0 or newer with GitHub Copilot enabled in a trusted workspace.
Node.js & npm: Node.js (≥ 20) and npm (≥ 9) installed and accessible on your system PATH.
Azure DevOps Access: Read access to the qcs-playwright-agent repository.

Quick Start Guide

Sign In & Connect:
- Open VS Code. If prompted, connect your Microsoft account to authenticate with Azure DevOps.
- You can also run QCS Playwright Automation: Connect ADO MCP from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
Verify Readiness:
- Check the Status Bar at the bottom of VS Code.
- It will display QCS Automation: ready when authentication and tools are loaded.
- If it displays degraded or error, click the status bar item or run QCS Playwright Automation: Run Setup Check.
Select Your Project Context:
- If your workspace was cloned from an Azure DevOps repository, your Organization and Project are detected automatically.
- If working in an unlinked folder, run QCS Playwright Automation: Select ADO Organization & Project to set your target project.
Generate Tests in Copilot Chat:
- Open GitHub Copilot Chat (Ctrl+Alt+I / Cmd+Alt+I).
- Prompt Copilot to create Playwright tests directly from an Azure DevOps Test Case or Work Item, for example:
  
  "Generate a Playwright test for ADO Test Case #12345"
  "Create Playwright specs for user login flow based on Work Item #67890"

Key Features

Automated Test Generation: Connects GitHub Copilot directly with Azure DevOps Test Plans, Test Cases, and Work Items to generate structured Playwright test scripts (.spec.ts).
Standardized Framework Scaffolding: Scans your workspace against QCS Playwright standards and automatically scaffolds missing helper files, page objects, and configurations.
Live Readiness & Status Indicators: Real-time status indicators in the VS Code status bar keep you informed of connectivity, authentication, and tool availability.
Automatic Organization & Project Detection: Automatically detects target Azure DevOps organizations and projects from workspace Git remotes.
Custom Branch Selection: Switch between agent prompt versions and framework updates on demand.
One-Click Diagnostics: Integrated setup checker verifies Node.js, npm, network transport, and authentication prerequisites with instant quick-fix actions.

Extension Commands

Access these commands anytime via the Command Palette (Ctrl+Shift+P / Cmd+Shift+P):

Command Title	Description
QCS Playwright Automation: Connect ADO MCP	Authenticates your Microsoft account with Azure DevOps.
QCS Playwright Automation: Restart ADO MCP Server	Re-connects and restarts the Azure DevOps integration if tools become unresponsive.
QCS Playwright Automation: Select ADO Organization & Project	Choose your target Azure DevOps Organization and Project for test generation.
QCS Playwright Automation: Scaffold Playwright Framework	Prepares or updates your workspace with standard QCS Playwright files and folder structures.
QCS Playwright Automation: Switch Agent Branch	Selects an alternate branch from the `qcs-playwright-agent` repository to fetch prompt rules and templates.
QCS Playwright Automation: Run Setup Check	Checks system prerequisites, Node.js versions, network connectivity, and authentication state.
QCS Playwright Automation: Show Logs	Opens the dedicated output log window for troubleshooting and diagnostics.

Settings & Customization

Customize extension preferences in VS Code Settings (Ctrl+, $\rightarrow$ search QCS Playwright):

Setting	Default	Description
`qcsPlaywrightAutomation.adoMcpMode`	`remote`	Transport mode (`remote` hosted endpoint or `local` package execution).
`qcsPlaywrightAutomation.adoOrg`	`EmersonAutomationSolutions`	Default Azure DevOps organization name.
`qcsPlaywrightAutomation.adoMcpTools`	`wit_get_work_item,wit_update_work_item`	Filter of specific ADO MCP tools exposed to Copilot Chat.
`qcsPlaywrightAutomation.agentBranch`	`master`	Git branch to load agent rules and framework templates from.
`qcsPlaywrightAutomation.verboseLogging`	`false`	Enables detailed diagnostic logging in the output channel.

Support & Troubleshooting

Contact & Support:
- For issues, questions, or engagement, reach out to [email protected].
Status indicates setup required or degraded:
1. Click the status bar item or run QCS Playwright Automation: Run Setup Check.
2. If authentication has expired or failed, run QCS Playwright Automation: Connect ADO MCP or QCS Playwright Automation: Restart ADO MCP Server.
Viewing Output Logs:
- Run QCS Playwright Automation: Show Logs from the Command Palette to inspect live diagnostic logs in the QCS Playwright Automation output channel.