π€ Awesome GitHub Copilot for Testers
This repository is a collection of resources (prompts, instructions, custom agents, agent skills, hooks, plugins, and orchestration examples) for using GitHub Copilot to enhance test automation and quality engineering workflows.
It is designed to help testers, developers, and quality engineers leverage AI to improve their testing practices, automate repetitive tasks, and enhance the overall quality of software products.
[!TIP] π‘ Choose your language:
[!TIP] This project is heavily inspired by Awesome GitHub Copilot - a curated list of resources for using GitHub Copilot effectively. We have adapted the structure and content to focus specifically on testing and quality engineering, providing tailored resources for this domain.
Table of Contents
[!IMPORTANT] Check out our free YouTube video to learn more about GitHub Copilot Chat Modes:
π― GitHub Copilot Customization Features
GitHub Copilot provides three main ways to customize AI responses and tailor assistance to your specific workflows, team guidelines, and project requirements:
- Custom Instructions: Define how Copilot should behave, what to prioritize, and how to communicate.
- Chat Modes: Create specialized chat modes for different roles or tasks, each with its own set of tools and instructions. With version 1.106 of VS Code, Chat Modes were renamed to Custom Agents.
- Custom Agents: Advanced chat modes that can utilize multiple instructions and tools to perform complex tasks.
- Prompt Templates: Predefined templates for common tasks or questions, allowing for quick and consistent responses.
[!TIP] More You can learn about these features in the official documentation and:
- VS Code Copilot Customization Documentation - Official Microsoft documentation
- Custom Instructions - Tailor Copilot's behavior
- Custom Chat Modes - Advanced chat configuration
- Custom Instructions - Customize Copilot's behavior
- Prompt Files - Using prompt templates
- Custom Agents - Advanced agent configuration
- Agent Skills - Extend agent capabilities with skills
- Hooks - Customize agent behavior with hooks
- Using agents in Visual Studio Code - Overview of agents and orchestration
- Subagents in Visual Studio Code - Using subagents for specialized tasks
[!TIP] Do you want to learn more about effective use of AI and GitHub Copilot for Testers?
Check our AI_Testers Program - a comprehensive Program for mastering AI in test automation!
π Resources
Custom Instructions
[!TIP] Usage:
- copy these instructions to your
.github/copilot-instructions.mdfile or- create task-specific
.github/.instructions.mdfiles in your workspace's.github/instructionsfolder- use
Chat: Attach Instructionscommand from the command palette to apply them in the current chat
| Title | Description | Install |
|---|---|---|
| π€ Custom Instructions for Testers | One-line intent of the rules | |
| API test rules (Playwright + TypeScript) | API test rules for Playwright + TypeScript: HTTP semantics, contract assertions, typed clients, data isolation, and flakiness prevention. | |
| Playwright E2E rules | Playwright E2E test rules: test intent, isolation, locator strategy, waiting discipline, flake prevention, and diagnostics. | |
| Page Objects / App Actions rules (Playwright + TS) | Page Object Model conventions for Playwright + TypeScript: structure, locators, actions, waits, and composition rules. | |
| Playwright Typescript | Playwright test generation instructions with best practices and patterns. | |
| TypeScript style rules | TypeScript style rules: explicit types at API boundaries, typed errors, import hygiene, and async conventions. |
Custom Prompt Templates
[!TIP] Usage:
- copy these prompts to your
.github/copilot-prompts/folder- use
/prompt-namein VS Code chat,- run
Chat: Run Promptcommand from the command palette
| Title | Description | Install |
|---|---|---|
| Accessibility audit β deep dive | Run a deeper accessibility audit for a page, sampled set of pages, or user flow with WCAG 2.2 mapping, manual verification guidance, and technical or stakeholder-ready output. For a quick single-URL check, use the a11y-webpage-audit prompt instead. | |
| A11y webpage audit (single URL) | Analyze one webpage for accessibility with WCAG 2.1/2.2 mapping and actionable fixes. Quick single-URL audit; use the a11y-audit-deep-dive prompt for multi-page flows and stakeholder-ready reporting. | |
| Analyze test results | Turn raw test run output β a CI log, JUnit/Playwright report, or console output β into an actionable summary: failure clusters, likely root-cause groups, flakiness suspects, and what to investigate first. | |
| API test plan and test generator | Create a risk-based API test plan and generate example automated tests from API definitions (OpenAPI/Postman/custom docs). API-focused end-to-end flow: plan first, then tests. | |
| Create a bug report | Turn rough tester notes, screenshots, logs, or observed behavior into a professional bug report with severity, reproducibility, and evidence guidance. | |
| Create a new skill | Create a new skill (SKILL.md) for VS Code Copilot. Analyzes existing skills for patterns, guides through design decisions, creates the skill file with supporting resources, and validates against best practices. | |
| Derive test cases from code | Read a function, module, or diff and derive white-box test cases from its actual branches, boundaries, and error paths β then compare against existing tests to expose coverage gaps. | |
| Analyze and explain code | Analyze and explain the selected code, the active file, or a provided snippet: purpose, structure, patterns, risks, and what a tester should verify | |
| Explain a test failure | Diagnose a failing test from an error message, stack trace, CI log, or trace file: classify the root cause as app defect, test bug, environment issue, or flakiness β without changing any code. Use the fix-tests prompt when you want the failure fixed. | |
| Fix failing tests | Diagnose and fix failing tests by addressing root causes, without weakening assertions or masking defects | |
| Generate exploratory testing charters | Create prioritized, timeboxed exploratory testing session charters from a feature description, release notes, or live app exploration β with risk focus, test ideas, and oracle notes for each session. | |
| Generate Gherkin scenarios | Convert a user story, acceptance criteria, or feature description into well-formed Gherkin scenarios (Given/When/Then) with scenario outlines for data variations, ready for BDD frameworks like Cucumber or Playwright-BDD. | |
| Generate test data | Design realistic and edge-covering test data packs from requirements, constraints, or existing test plans for manual and automated testing. | |
| Generate manual test cases | Turn a feature description, acceptance criteria, exploratory notes, or a test plan into detailed manual test cases with risk tags, expected results, and automation hints. | |
| Map requirements to test coverage | Build a Requirements Traceability Matrix from a PRD, user stories, or acceptance criteria against existing tests: what is covered, at which level, what is missing, and which gaps carry the most risk. | |
| Migrate tests to Playwright | Migrate existing UI tests from Cypress, Selenium, Puppeteer, or Protractor to Playwright while preserving coverage: translate idioms to Playwright best practices, run both suites where possible, and report an honest migration status per test. | |
| Performance and reliability test planner | Design a performance and reliability test strategy and propose concrete load/soak tests for critical user flows. | |
| Explore a website and gather network requests using Playwright MCP | Explore a website with Playwright MCP while capturing network requests and responses. Use the playwright-explore-website prompt instead when network traffic is not needed. | |
| Explore a website and propose test cases | Explore a website with Playwright MCP and propose test cases. Use the playwright-explore-website-requests prompt instead when network traffic should also be captured. | |
| Generate tests based on a scenario using Playwright MCP | Generate a Playwright test from a scenario description by first executing it live via Playwright MCP. Use the test-generator prompt instead when generating from a written test plan file. | |
| QA strategy β edge cases, security and attack scenarios | For any feature, user story, or API spec: instantly generate a structured scenario matrix covering edge cases, boundary values, OWASP Top 10 security attacks, and adversarial sequences. | |
| Refactor tests to page objects | Refactor UI test specs into a clean Page Object Model without changing what the tests verify: extract locators and actions, keep assertions in tests, and prove behavior is unchanged by rerunning the suite. | |
| Analyze regression scope | Turn a diff, PR summary, changed files, or hotfix description into a prioritized regression scope with a minimal confidence suite and retest guidance. | |
| Review requirements for testability | Review a user story, PRD, or acceptance criteria for ambiguity, missing states, and untestable statements β before implementation starts. Produces concrete clarifying questions and rewritten, testable acceptance criteria. | |
| Stabilize flaky tests | Hunt down intermittently failing tests, classify the flakiness root cause (timing, environment, data, state leakage), fix it properly, and prove stability with repeated runs. Use the fix-tests prompt for tests that fail consistently. | |
| Tech debt audit β test automation code review | Ruthlessly audit automated test code for anti-patterns: fragile selectors, hardcoded waits, missing assertions, test interdependencies, credential leaks, and more. Produces a severity-ranked debt report with line-level citations and concrete fixes. | |
| Generate tests based on test plan | Generate automated tests from a written test plan file, matching the project's existing framework. Use the playwright-generate-test prompt instead when starting from a scenario description. | |
| Generate a basic test plan | Generate a quick, single-pass test plan for a website from light exploration. Use the test-planner prompt for a comprehensive, interactive |

No comments yet
Be the first to share your take.