Azure Pipeline<\/a> to execute them as part of it, on regular basis.<\/p>\nMake sure to tailor the prompts to your specific needs and context – this will help Copilot generate higher-quality scripts.<\/p>\n
Prompt 1:<\/strong><\/p>\nGet me the details of the test cases (do not action anything yet, just give me the details of each test case).\n\nTest Information:\n\n* ADO Organization: Org_Name\n\n* Project: Project_Name\n\n* Test Plan ID: Test_Plan_ID\n\n* Test Suite ID: Test_Suite_ID\n\n<\/code><\/pre>\nAfter Copilot gets the details for each test case, via the MCP server, use the following prompt:<\/p>\n
Prompt 2:<\/strong><\/p>\nImagine you are an experienced Software Engineer helping me write high-quality Playwright test scripts in TypeScript based on the test cases I provided. Please go over the task twice to make sure the scripts are accurate and reliable. Avoid making things up and do no hallucinate. Use all the extra information outlined below, to write the best possible scripts, tailored for my project.\n\n# Project Context\n\nLook at the \"Project_name\" folder, to get more insights (if your project is quite large, use the below section to be more concrete and reference specific folders\/files).\n\nMy project structure includes:\n\n* Authentication helpers: \/\/*Add\/folder\/path*\n\n* Existing sample tests: \/\/*Add\/folder\/path*\n\n* Playwright config: \/\/*Add\/folder\/path*\n\n* Test Structure: \/\/*Add\/folder\/path\/test-1656280.spec.ts*\n\n* The project\u2019s UX components are in the following folder: \/\/*Add\/folder\/path*.\n\n# Test Structure Requirements\n\nFor each test, please follow this structure:\n\n1. Clear test description using *'test.describe()'* blocks\n\n2. Proper authentication setup before any page navigation\n\n3. Robust selector strategies with multiple fallbacks\n\n4. Detailed logging for debugging\n\n5. Screenshot captures at key points for verification\n\n6. Proper error handling with clear error messages\n\n7. Appropriate timeouts and wait strategies\n\n8. Verification\/assertion steps that match the test case acceptance criteria\n\n# Robustness Requirements\n\nEach test should include:\n\n1. Retry mechanisms for flaky UI elements\n\n2. Multiple selector strategies to find elements\n\n3. Explicit waits for network idle and page load states\n\n4. Clear logging of each test step\n\n5. Detailed error reporting and screenshots on failure\n\n6. Handling of unexpected dialogs or notifications\n\n7. Timeout handling with clear error messages\n\n# Environmental Considerations\n\nThe tests will run in:\n\n* CI\/CD pipeline environments\n\n* Headless mode by default\n\n* Potentially with network latency\n\n* Different viewport sizes\n\n# Example Usage\n\nPlease provide a complete implementation with:\n\n1. Helper functions for authentication and common operations\n\n2. Full test implementation for each test case\n\n3. Comments explaining complex logic\n\n4. Guidance on test execution\n\n# Authentication Approach\n\nIn order for the tests to be executed, we need to authenticate the application. Use the below auth approach:\n\n\/\/{you need to define the authentication steps \u2013 if this is already defined for your project, instruct Copilot how to use it. If your scenarios do not require auth, you can remove this part from the prompt.}\n\n# Configuration Reference\n\nFor timeouts, screenshot settings, and other configuration options, please refer to:\n\n\/\/{Add a reference to a specific file, etc. for better context}\n\nI want these tests to be maintainable, reliable, and provide clear feedback when they fail.<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"In today\u2019s fast-paced software development cycles, manual testing often becomes a significant bottleneck. Our team was facing a growing backlog of test cases that required repetitive manual execution\u2014running the entire test suite every sprint. This consumed valuable time that could be better spent on exploratory testing and higher-value tasks. We set out to solve this […]<\/p>\n","protected":false},"author":176848,"featured_media":71385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,252],"tags":[7287,7262],"class_list":["post-71324","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-testing","tag-automated-testing","tag-azure-devops"],"acf":[],"blog_post_summary":"
In today\u2019s fast-paced software development cycles, manual testing often becomes a significant bottleneck. Our team was facing a growing backlog of test cases that required repetitive manual execution\u2014running the entire test suite every sprint. This consumed valuable time that could be better spent on exploratory testing and higher-value tasks. We set out to solve this […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/71324","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/176848"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=71324"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/71324\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/71385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=71324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=71324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=71324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2025\/06\/Screenshot-2025-06-26-at-8.58.38.png\")
<\/a><\/p>\n![\"A](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2025\/07\/example-test-case-steps.png\")
<\/p>\n