Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-23 20:05:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add Playwright MCP prompts and chat modes for testing and automation (#99)

Browse Source 
* Add Playwright MCP prompts and chat modes for testing and automation

* Update prompts/playwright-generate-test.prompt.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Enhance Playwright prompts and chatmode descriptions for clarity and consistency

* Add model specification to Playwright tester chatmode

* Update model specification in Playwright test generation prompt

* Add description to Playwright test generation prompt

* Refactor Playwright tools list in prompts and chat modes to remove redundant entries as just adding playwright seems to be supported now

* Fix typo in Playwright tester responsibilities section

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
This commit is contained in:
Debbie O'Brien
2025-07-28 01:57:29 +02:00
committed by GitHub
parent ce36c84810
commit edb5e16922
5 changed files with 85 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
prompts/playwright-explore-website.prompt.md Normal file
View File

@@ -0,0 +1,19 @@
---
mode: agent
description: 'Website exploration for testing using Playwright MCP'
tools: ['changes', 'codebase', 'editFiles', 'fetch', 'findTestFiles', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'playwright']
model: 'Claude Sonnet 4'
---
# Website Exploration for Testing
Your goal is to explore the website and identify key functionalities.
## Specific Instructions
1. Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
2. Identify and interact with 3-5 core features or user flows.
3. Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
4. Close the browser context upon completion.
5. Provide a concise summary of your findings.
6. Propose and generate test cases based on the exploration.