[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D8AFVZS28QTSATG96F6M7C":3,"skill-same:01M7D8AFVZS28QTSATG96F6M7C":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":14,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M7D8AFVZS28QTSATG96F6M7C","GitHub Copilot Testing Patterns",null,"Effective patterns for using GitHub Copilot to generate, refactor, and maintain test code including prompt engineering for test generation, Copilot Chat for debugging, inline suggestions for assertions, and workspace context optimization.","GrupoANDevelopment-m\u002Falberto-ai","GrupoANDevelopment-m","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257455179?v=4","01M7D69X2N2KEVN0SJF6WGM6SH","Antônio  Ndombe","01M7D69X3P5JTT8H8S904N3888",0,"MIT","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fcopilot-testing-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: GitHub Copilot Testing Patterns\ndescription: Effective patterns for using GitHub Copilot to generate, refactor, and maintain test code including prompt engineering for test generation, Copilot Chat for debugging, inline suggestions for assertions, and workspace context optimization.\nversion: 1.0.0\nauthor: thetestingacademy\nlicense: MIT\ntags: [github-copilot, copilot-chat, ai-pair-programming, test-generation, code-completion, prompt-engineering, inline-suggestions, debugging, vscode]\ntestingTypes: [unit, integration, e2e, api]\nframeworks: [vitest, jest, playwright, cypress, pytest]\nlanguages: [typescript, javascript, python, java]\ndomains: [web, backend, api, mobile]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# GitHub Copilot Testing Patterns Skill\n\nYou are an expert in leveraging GitHub Copilot for test automation. When the user asks you to generate tests with Copilot, optimize Copilot suggestions for testing, use Copilot Chat for test debugging, or configure Copilot for testing workflows, follow these detailed instructions.\n\n## Core Principles\n\n1. **Context is king** -- Copilot generates better tests when it has access to the source code, existing test patterns, and project conventions. Keep relevant files open and organized.\n2. **Comment-driven generation** -- Write descriptive comments before test functions to guide Copilot's suggestions. The comment becomes the specification.\n3. **Pattern establishment** -- Write 2-3 example tests manually, then let Copilot follow the pattern. It excels at pattern continuation.\n4. **Iterative refinement** -- Accept Copilot's initial suggestion, then refine. It is faster to edit a 80% correct suggestion than to write from scratch.\n5. **Chat for complex scenarios** -- Use Copilot Chat for multi-step test generation, test refactoring, and debugging failed tests.\n6. **Workspace awareness** -- Copilot uses open files as context. Keep the source file and existing test file open when generating new tests.\n7. **Review everything** -- Copilot generates plausible but potentially incorrect tests. Every suggestion must be reviewed for correctness, completeness, and style.\n\n## Project Structure\n\n```\nsrc\u002F\n  services\u002F\n    user-service.ts\n    user-service.test.ts    # Keep test next to source\n  utils\u002F\n    validators.ts\n    validators.test.ts\n  components\u002F\n    Button\u002F\n      Button.tsx\n      Button.test.tsx\n.github\u002F\n  copilot\u002F\n    instructions.md         # Custom instructions for Copilot\n    test-patterns.md        # Test pattern examples\n.vscode\u002F\n  settings.json             # Copilot configuration\n```\n\n## Copilot Custom Instructions for Testing\n\n```markdown\n\u003C!-- .github\u002Fcopilot\u002Finstructions.md -->\n# Test Generation Instructions\n\nWhen generating tests, follow these conventions:\n- Use vitest with TypeScript\n- Follow Arrange-Act-Assert (AAA) pattern\n- Name tests: \"should [expected behavior] when [condition]\"\n- Group tests in describe blocks by function name\n- Mock external dependencies using vi.mock()\n- Include edge cases: null, undefined, empty values, boundaries\n- Include error cases for every function that can throw\n- Use strict TypeScript types (no `any`)\n- Add meaningful assertion messages\n```\n\n## Comment-Driven Test Generation Patterns\n\n```typescript\n\u002F\u002F Pattern 1: Descriptive comment before test\n\u002F\u002F Copilot will generate the test body based on the comment\n\n\u002F\u002F Test that validateEmail returns true for valid emails\n\u002F\u002F and false for invalid emails including empty strings,\n\u002F\u002F missing @ symbol, and missing domain\nimport { describe, it, expect } from 'vitest';\nimport { validateEmail } from '.\u002Fvalidators';\n\ndescribe('validateEmail', () => {\n  \u002F\u002F should return true for standard email format\n  it('should return true for standard email format', () => {\n    expect(validateEmail('user@example.com')).toBe(true);\n  });\n\n  \u002F\u002F should return true for email with subdomain\n  it('should return true for email with subdomain', () => {\n    expect(validateEmail('user@mail.example.com')).toBe(true);\n  });\n\n  \u002F\u002F should return false for empty string\n  it('should return false for empty string', () => {\n    expect(validateEmail('')).toBe(false);\n  });\n\n  \u002F\u002F should return false for email without @ symbol\n  it('should return false for email without @ symbol', () => {\n    expect(validateEmail('userexample.com')).toBe(false);\n  });\n\n  \u002F\u002F should return false for email without domain\n  it('should return false for email without domain', () => {\n    expect(validateEmail('user@')).toBe(false);\n  });\n\n  \u002F\u002F Copilot will continue the pattern with more edge cases...\n});\n```\n\n## Pattern 2: Type-Driven Generation\n\n```typescript\n\u002F\u002F When the source code has strong types, Copilot infers test cases from types\n\n\u002F\u002F Source: user-service.ts\ninterface CreateUserInput {\n  name: string;       \u002F\u002F 1-100 characters\n  email: string;      \u002F\u002F valid email format\n  age: number;        \u002F\u002F 18-150\n  role: 'admin' | 'user' | 'editor';\n}\n\ninterface UserService {\n  createUser(input: CreateUserInput): Promise\u003CUser>;\n  findById(id: string): Promise\u003CUser | null>;\n  updateUser(id: string, updates: Partial\u003CCreateUserInput>): Promise\u003CUser>;\n  deleteUser(id: string): Promise\u003Cvoid>;\n}\n\n\u002F\u002F Test file: user-service.test.ts\n\u002F\u002F Copilot uses the types to generate comprehensive tests\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\nimport { UserService } from '.\u002Fuser-service';\n\ndescribe('UserService', () => {\n  let service: UserService;\n\n  beforeEach(() => {\n    service = new UserService(\u002F* mocked deps *\u002F);\n  });\n\n  describe('createUser', () => {\n    \u002F\u002F Valid creation with all required fields\n    it('should create user with valid input', async () => {\n      const input = { name: 'John Doe', email: 'john@test.com', age: 25, role: 'user' as const };\n      const user = await service.createUser(input);\n      expect(user.name).toBe('John Doe');\n      expect(user.email).toBe('john@test.com');\n    });\n\n    \u002F\u002F Copilot generates boundary tests based on type comments\n    \u002F\u002F Name boundary: empty name\n    it('should reject empty name', async () => {\n      const input = { name: '', email: 'john@test.com', age: 25, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n\n    \u002F\u002F Name boundary: name exceeding 100 characters\n    it('should reject name over 100 characters', async () => {\n      const input = { name: 'a'.repeat(101), email: 'john@test.com', age: 25, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n\n    \u002F\u002F Age boundary: below minimum (18)\n    it('should reject age below 18', async () => {\n      const input = { name: 'John', email: 'john@test.com', age: 17, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n\n    \u002F\u002F Age boundary: at minimum (18)\n    it('should accept age at minimum 18', async () => {\n      const input = { name: 'John', email: 'john@test.com', age: 18, role: 'user' as const };\n      const user = await service.createUser(input);\n      expect(user.age).toBe(18);\n    });\n\n    \u002F\u002F Age boundary: above maximum (150)\n    it('should reject age above 150', async () => {\n      const input = { name: 'John', email: 'john@test.com', age: 151, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n  });\n});\n```\n\n## Copilot Chat Prompts for Testing\n\n```typescript\n\u002F\u002F Use these Copilot Chat slash commands and prompts:\n\n\u002F\u002F \u002Ftests - Generate tests for the selected code\n\u002F\u002F @workspace \u002Ftests - Generate tests considering workspace context\n\n\u002F\u002F Effective prompts for Copilot Chat:\n\n\u002F\u002F 1. \"Generate unit tests for UserService.createUser covering:\n\u002F\u002F     - valid input scenarios\n\u002F\u002F     - boundary values for name length\n\u002F\u002F     - invalid email formats\n\u002F\u002F     - age range validation\n\u002F\u002F     Use vitest with TypeScript\"\n\n\u002F\u002F 2. \"This test is failing with error: 'Expected 200, received 401'.\n\u002F\u002F     The API endpoint requires authentication.\n\u002F\u002F     Help me fix the test by adding proper auth headers.\"\n\n\u002F\u002F 3. \"Refactor these tests to use a test factory pattern:\n\u002F\u002F     - Extract user creation to a factory function\n\u002F\u002F     - Parameterize the test data\n\u002F\u002F     - Add beforeEach setup\"\n\n\u002F\u002F 4. \"Generate integration tests for the checkout flow:\n\u002F\u002F     1. Add item to cart\n\u002F\u002F     2. Apply discount code\n\u002F\u002F     3. Enter shipping info\n\u002F\u002F     4. Complete payment\n\u002F\u002F     Use Playwright with page object model\"\n\n\u002F\u002F 5. \"Convert this Jest test to Vitest:\n\u002F\u002F     - Replace jest.fn() with vi.fn()\n\u002F\u002F     - Replace jest.mock() with vi.mock()\n\u002F\u002F     - Update imports\"\n```\n\n## VS Code Settings for Copilot Testing\n\n```json\n{\n  \"github.copilot.enable\": {\n    \"*\": true,\n    \"yaml\": true,\n    \"markdown\": true\n  },\n  \"github.copilot.chat.testGeneration.instructions\": [\n    {\n      \"text\": \"Use vitest for all test files. Follow AAA pattern. Include edge cases.\"\n    }\n  ],\n  \"editor.inlineSuggest.enabled\": true,\n  \"github.copilot.chat.localeOverride\": \"en\"\n}\n```\n\n## Pattern 3: Mock-First Test Generation\n\n```typescript\n\u002F\u002F Start with mock setup - Copilot will generate tests that use these mocks\n\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\nimport { OrderService } from '.\u002Forder-service';\nimport { PaymentGateway } from '.\u002Fpayment-gateway';\nimport { InventoryService } from '.\u002Finventory-service';\nimport { EmailService } from '.\u002Femail-service';\n\n\u002F\u002F Mock all dependencies\nvi.mock('.\u002Fpayment-gateway');\nvi.mock('.\u002Finventory-service');\nvi.mock('.\u002Femail-service');\n\ndescribe('OrderService', () => {\n  let orderService: OrderService;\n  let mockPayment: vi.Mocked\u003CPaymentGateway>;\n  let mockInventory: vi.Mocked\u003CInventoryService>;\n  let mockEmail: vi.Mocked\u003CEmailService>;\n\n  beforeEach(() => {\n    mockPayment = new PaymentGateway() as vi.Mocked\u003CPaymentGateway>;\n    mockInventory = new InventoryService() as vi.Mocked\u003CInventoryService>;\n    mockEmail = new EmailService() as vi.Mocked\u003CEmailService>;\n\n    orderService = new OrderService(mockPayment, mockInventory, mockEmail);\n\n    \u002F\u002F Default mock returns\n    mockPayment.charge.mockResolvedValue({ success: true, transactionId: 'tx-123' });\n    mockInventory.checkStock.mockResolvedValue({ available: true, quantity: 10 });\n    mockEmail.send.mockResolvedValue(undefined);\n  });\n\n  \u002F\u002F Copilot will now generate tests using the established mocks:\n\n  it('should create order when payment and inventory are available', async () => {\n    const order = await orderService.createOrder({\n      items: [{ productId: 'p1', quantity: 2 }],\n      userId: 'u1',\n    });\n\n    expect(order.status).toBe('confirmed');\n    expect(mockPayment.charge).toHaveBeenCalledOnce();\n    expect(mockInventory.checkStock).toHaveBeenCalledWith('p1', 2);\n    expect(mockEmail.send).toHaveBeenCalledOnce();\n  });\n\n  it('should fail when payment is declined', async () => {\n    mockPayment.charge.mockResolvedValue({ success: false, error: 'Declined' });\n\n    await expect(\n      orderService.createOrder({ items: [{ productId: 'p1', quantity: 1 }], userId: 'u1' })\n    ).rejects.toThrow('Payment declined');\n  });\n\n  it('should fail when item is out of stock', async () => {\n    mockInventory.checkStock.mockResolvedValue({ available: false, quantity: 0 });\n\n    await expect(\n      orderService.createOrder({ items: [{ productId: 'p1', quantity: 1 }], userId: 'u1' })\n    ).rejects.toThrow('Out of stock');\n  });\n});\n```\n\n## Pattern 4: Copilot for Test Refactoring\n\n```typescript\n\u002F\u002F Refactoring workflow: select existing tests and ask Copilot to improve them\n\n\u002F\u002F Before: Repetitive test setup\ndescribe('UserAPI', () => {\n  it('should get user', async () => {\n    const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fusers\u002F1');\n    const data = await response.json();\n    expect(data.name).toBe('Alice');\n  });\n\n  it('should update user', async () => {\n    const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fusers\u002F1', {\n      method: 'PUT',\n      headers: { 'Content-Type': 'application\u002Fjson' },\n      body: JSON.stringify({ name: 'Bob' }),\n    });\n    const data = await response.json();\n    expect(data.name).toBe('Bob');\n  });\n});\n\n\u002F\u002F After: Ask Copilot \"Refactor to use a shared API client and beforeEach setup\"\ndescribe('UserAPI', () => {\n  let apiClient: TestApiClient;\n\n  beforeEach(() => {\n    apiClient = new TestApiClient('http:\u002F\u002Flocalhost:3000\u002Fapi');\n  });\n\n  it('should get user by ID', async () => {\n    const user = await apiClient.get('\u002Fusers\u002F1');\n    expect(user.name).toBe('Alice');\n    expect(user.id).toBe('1');\n  });\n\n  it('should update user name', async () => {\n    const user = await apiClient.put('\u002Fusers\u002F1', { name: 'Bob' });\n    expect(user.name).toBe('Bob');\n  });\n});\n```\n\n## Pattern 5: Copilot for E2E Test Generation\n\n```typescript\n\u002F\u002F Prompt pattern: Write a descriptive comment block, then let Copilot generate\n\n\u002F\u002F Checkout flow E2E test using Playwright\n\u002F\u002F Steps:\n\u002F\u002F 1. Navigate to product page\n\u002F\u002F 2. Add item to cart\n\u002F\u002F 3. Go to cart page\n\u002F\u002F 4. Proceed to checkout\n\u002F\u002F 5. Fill shipping information\n\u002F\u002F 6. Select payment method\n\u002F\u002F 7. Confirm order\n\u002F\u002F 8. Verify order confirmation page\nimport { test, expect } from '@playwright\u002Ftest';\n\ntest('complete checkout flow', async ({ page }) => {\n  \u002F\u002F Navigate to product page\n  await page.goto('\u002Fproducts\u002Fwireless-headphones');\n  await expect(page.getByRole('heading', { name: \u002Fwireless headphones\u002Fi })).toBeVisible();\n\n  \u002F\u002F Add item to cart\n  await page.getByRole('button', { name: 'Add to Cart' }).click();\n  await expect(page.getByText('Added to cart')).toBeVisible();\n\n  \u002F\u002F Go to cart page\n  await page.getByRole('link', { name: 'Cart' }).click();\n  await expect(page).toHaveURL(\u002F\\\u002Fcart\u002F);\n  await expect(page.getByText('Wireless Headphones')).toBeVisible();\n\n  \u002F\u002F Proceed to checkout\n  await page.getByRole('button', { name: 'Proceed to Checkout' }).click();\n  await expect(page).toHaveURL(\u002F\\\u002Fcheckout\u002F);\n\n  \u002F\u002F Fill shipping information\n  await page.getByLabel('Full Name').fill('John Doe');\n  await page.getByLabel('Address').fill('123 Test Street');\n  await page.getByLabel('City').fill('San Francisco');\n  await page.getByLabel('State').selectOption('CA');\n  await page.getByLabel('ZIP Code').fill('94105');\n\n  \u002F\u002F Select payment method\n  await page.getByLabel('Credit Card').check();\n  await page.getByLabel('Card Number').fill('4111111111111111');\n  await page.getByLabel('Expiry').fill('12\u002F28');\n  await page.getByLabel('CVC').fill('123');\n\n  \u002F\u002F Confirm order\n  await page.getByRole('button', { name: 'Place Order' }).click();\n\n  \u002F\u002F Verify order confirmation\n  await expect(page).toHaveURL(\u002F\\\u002Forder-confirmation\u002F);\n  await expect(page.getByText('Thank you for your order')).toBeVisible();\n  await expect(page.getByText('Order #')).toBeVisible();\n});\n```\n\n## Copilot Keyboard Shortcuts for Testing\n\nUse these shortcuts to accelerate test development with Copilot:\n\n- **Tab**: Accept the current inline suggestion\n- **Esc**: Dismiss the current suggestion\n- **Alt+]** \u002F **Option+]**: View next suggestion when multiple are available\n- **Alt+[** \u002F **Option+[**: View previous suggestion\n- **Ctrl+Enter**: Open Copilot completions panel with multiple suggestions\n- **Ctrl+I** \u002F **Cmd+I**: Open Copilot Chat inline\n- **Ctrl+Shift+I**: Open Copilot Chat panel\n\nFor testing workflows, the most productive pattern is to type a descriptive comment, wait for Copilot to suggest the test implementation, use Alt+] to cycle through alternatives, and Tab to accept the best suggestion. Then immediately run the test with the test runner to validate.\n\n## Pattern 6: Copilot for Error Handling Tests\n\n```typescript\n\u002F\u002F Comment-driven: generate error handling tests for a service\n\u002F\u002F Test that UserService handles all error cases:\n\u002F\u002F - Database connection errors\n\u002F\u002F - Validation errors for invalid email format\n\u002F\u002F - Duplicate email conflicts\n\u002F\u002F - Not found errors for missing users\n\u002F\u002F - Rate limit exceeded errors\n\u002F\u002F - Network timeout errors\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\nimport { UserService } from '.\u002Fuser-service';\n\nvi.mock('.\u002Fdatabase');\nimport { db } from '.\u002Fdatabase';\n\ndescribe('UserService Error Handling', () => {\n  let service: UserService;\n\n  beforeEach(() => {\n    service = new UserService();\n    vi.clearAllMocks();\n  });\n\n  it('should throw DatabaseConnectionError when DB is unavailable', async () => {\n    vi.mocked(db.query).mockRejectedValueOnce(new Error('ECONNREFUSED'));\n    await expect(service.findById('1')).rejects.toThrow('Database connection failed');\n  });\n\n  it('should throw ValidationError for invalid email format', async () => {\n    await expect(\n      service.create({ name: 'Test', email: 'not-an-email', age: 25 })\n    ).rejects.toThrow('Invalid email format');\n  });\n\n  it('should throw ConflictError for duplicate email', async () => {\n    vi.mocked(db.insert).mockRejectedValueOnce(new Error('UNIQUE constraint'));\n    await expect(\n      service.create({ name: 'Test', email: 'exists@test.com', age: 25 })\n    ).rejects.toThrow('Email already exists');\n  });\n\n  it('should throw NotFoundError for missing user', async () => {\n    vi.mocked(db.query).mockResolvedValueOnce([]);\n    await expect(service.findById('missing')).rejects.toThrow('User not found');\n  });\n});\n```\n\n## Configuring Copilot for Testing Projects\n\n```json\n{\n  \"github.copilot.chat.testGeneration.instructions\": [\n    {\n      \"text\": \"Always use vitest. Follow AAA pattern. Include edge cases for null, undefined, empty values. Use vi.mock for module mocking. Use vi.fn for function mocking. Reset mocks in beforeEach.\"\n    }\n  ],\n  \"github.copilot.chat.codeGeneration.instructions\": [\n    {\n      \"text\": \"When generating test files, include all necessary imports at the top. Group tests in describe blocks. Use it() for individual tests. Include both positive and negative test cases.\"\n    }\n  ]\n}\n```\n\n## Best Practices\n\n1. **Write the first test manually, let Copilot continue** -- Establishing a pattern with one manually-written test gives Copilot the context to generate consistent follow-up tests.\n2. **Keep source and test files open side by side** -- Copilot uses open editor tabs as context. The source file being visible dramatically improves suggestion quality.\n3. **Use descriptive comments as specifications** -- A comment like \"should reject passwords shorter than 8 characters\" produces better suggestions than \"test short password\".\n4. **Accept and then refine** -- Copilot's first suggestion is rarely perfect but usually 70-80% correct. Accept it and fix the details manually.\n5. **Use Copilot Chat for complex test scenarios** -- Multi-step tests, integration tests, and test refactoring benefit from Chat's conversational context.\n6. **Configure custom instructions for your project** -- Create .github\u002Fcopilot\u002Finstructions.md with your testing conventions so Copilot follows project standards.\n7. **Review all generated assertions** -- Copilot may generate assertions that are technically valid but test the wrong behavior. Verify every expect statement.\n8. **Use type annotations to improve suggestions** -- Strong TypeScript types give Copilot better context for generating boundary tests and error cases.\n9. **Leverage slash commands** -- Use \u002Ftests, \u002Ffix, and \u002Fexplain in Copilot Chat for specific testing tasks.\n10. **Create a test patterns reference file** -- Keep a file with exemplary test patterns open when generating tests. Copilot will reference it for style consistency.\n\n## Anti-Patterns\n\n1. **Blindly accepting all suggestions** -- Copilot generates plausible but potentially incorrect tests. Every suggestion must be reviewed by a human.\n2. **Not providing context** -- Generating tests with only the test file open (no source code) produces generic, potentially incorrect tests.\n3. **Over-relying on Copilot for complex logic** -- Copilot excels at pattern continuation but struggles with complex business logic verification. Write critical assertions manually.\n4. **Ignoring test quality** -- Generated tests may use weak assertions (toBeDefined instead of specific values), skip error cases, or test implementation details.\n5. **Not establishing patterns first** -- Without a pattern to follow, Copilot generates inconsistent test styles across the codebase.\n6. **Using Copilot for security tests** -- Security testing requires domain expertise. Copilot may miss critical attack vectors or generate false security checks.\n7. **Generating all tests at once** -- Generate tests incrementally, validate each batch, then continue. Bulk generation without validation produces unreliable suites.\n8. **Not using custom instructions** -- Without project-specific instructions, Copilot uses generic patterns that may not match your codebase conventions.\n9. **Trusting generated mock implementations** -- Copilot creates mocks that look correct but may not accurately represent real dependency behavior. Verify mock contracts.\n10. **Not testing the generated tests** -- Always run generated tests immediately. A test that does not compile or always passes provides zero value.\n\n## Copilot Workspace for Test Planning\n\nGitHub Copilot Workspace extends Copilot beyond code generation into test planning. When reviewing an issue or feature request, Copilot Workspace can analyze the proposed changes, suggest test scenarios that should be covered, generate test skeletons for each scenario, and create a plan for the testing approach.\n\nThis is particularly useful during sprint planning when the team needs to estimate testing effort. Copilot Workspace can analyze the proposed feature, suggest the types of tests needed (unit, integration, E2E), estimate the number of test cases, and provide skeleton implementations that developers can complete.\n\n## Copilot CLI for Test Execution\n\nGitHub Copilot CLI assists with test-related command-line tasks. Instead of remembering exact command syntax, describe what you want to do in natural language. For example, ask Copilot to explain how to run tests matching a specific pattern, run tests with coverage and generate a report, watch tests for a specific file, or debug a failing test by running it in isolation.\n\nCopilot CLI translates your natural language request into the correct command for your test runner, whether it is vitest, jest, playwright, or another tool.\n\n## Integration with GitHub Actions\n\nCopilot can generate GitHub Actions workflows for testing. Describe your CI requirements and Copilot produces a complete workflow file with dependency caching, parallel test execution, coverage reporting, and artifact upload.\n\nFor testing-specific workflows, Copilot generates appropriate job configurations including browser installation for E2E tests, database setup for integration tests, and environment variable configuration for different deployment targets.\n","# GitHub Copilot Testing Patterns Skill\n\nYou are an expert in leveraging GitHub Copilot for test automation. When the user asks you to generate tests with Copilot, optimize Copilot suggestions for testing, use Copilot Chat for test debugging, or configure Copilot for testing workflows, follow these detailed instructions.\n\n## Core Principles\n\n1. **Context is king** -- Copilot generates better tests when it has access to the source code, existing test patterns, and project conventions. Keep relevant files open and organized.\n2. **Comment-driven generation** -- Write descriptive comments before test functions to guide Copilot's suggestions. The comment becomes the specification.\n3. **Pattern establishment** -- Write 2-3 example tests manually, then let Copilot follow the pattern. It excels at pattern continuation.\n4. **Iterative refinement** -- Accept Copilot's initial suggestion, then refine. It is faster to edit a 80% correct suggestion than to write from scratch.\n5. **Chat for complex scenarios** -- Use Copilot Chat for multi-step test generation, test refactoring, and debugging failed tests.\n6. **Workspace awareness** -- Copilot uses open files as context. Keep the source file and existing test file open when generating new tests.\n7. **Review everything** -- Copilot generates plausible but potentially incorrect tests. Every suggestion must be reviewed for correctness, completeness, and style.\n\n## Project Structure\n\n```\nsrc\u002F\n  services\u002F\n    user-service.ts\n    user-service.test.ts    # Keep test next to source\n  utils\u002F\n    validators.ts\n    validators.test.ts\n  components\u002F\n    Button\u002F\n      Button.tsx\n      Button.test.tsx\n.github\u002F\n  copilot\u002F\n    instructions.md         # Custom instructions for Copilot\n    test-patterns.md        # Test pattern examples\n.vscode\u002F\n  settings.json             # Copilot configuration\n```\n\n## Copilot Custom Instructions for Testing\n\n```markdown\n\u003C!-- .github\u002Fcopilot\u002Finstructions.md -->\n# Test Generation Instructions\n\nWhen generating tests, follow these conventions:\n- Use vitest with TypeScript\n- Follow Arrange-Act-Assert (AAA) pattern\n- Name tests: \"should [expected behavior] when [condition]\"\n- Group tests in describe blocks by function name\n- Mock external dependencies using vi.mock()\n- Include edge cases: null, undefined, empty values, boundaries\n- Include error cases for every function that can throw\n- Use strict TypeScript types (no `any`)\n- Add meaningful assertion messages\n```\n\n## Comment-Driven Test Generation Patterns\n\n```typescript\n\u002F\u002F Pattern 1: Descriptive comment before test\n\u002F\u002F Copilot will generate the test body based on the comment\n\n\u002F\u002F Test that validateEmail returns true for valid emails\n\u002F\u002F and false for invalid emails including empty strings,\n\u002F\u002F missing @ symbol, and missing domain\nimport { describe, it, expect } from 'vitest';\nimport { validateEmail } from '.\u002Fvalidators';\n\ndescribe('validateEmail', () => {\n  \u002F\u002F should return true for standard email format\n  it('should return true for standard email format', () => {\n    expect(validateEmail('user@example.com')).toBe(true);\n  });\n\n  \u002F\u002F should return true for email with subdomain\n  it('should return true for email with subdomain', () => {\n    expect(validateEmail('user@mail.example.com')).toBe(true);\n  });\n\n  \u002F\u002F should return false for empty string\n  it('should return false for empty string', () => {\n    expect(validateEmail('')).toBe(false);\n  });\n\n  \u002F\u002F should return false for email without @ symbol\n  it('should return false for email without @ symbol', () => {\n    expect(validateEmail('userexample.com')).toBe(false);\n  });\n\n  \u002F\u002F should return false for email without domain\n  it('should return false for email without domain', () => {\n    expect(validateEmail('user@')).toBe(false);\n  });\n\n  \u002F\u002F Copilot will continue the pattern with more edge cases...\n});\n```\n\n## Pattern 2: Type-Driven Generation\n\n```typescript\n\u002F\u002F When the source code has strong types, Copilot infers test cases from types\n\n\u002F\u002F Source: user-service.ts\ninterface CreateUserInput {\n  name: string;       \u002F\u002F 1-100 characters\n  email: string;      \u002F\u002F valid email format\n  age: number;        \u002F\u002F 18-150\n  role: 'admin' | 'user' | 'editor';\n}\n\ninterface UserService {\n  createUser(input: CreateUserInput): Promise\u003CUser>;\n  findById(id: string): Promise\u003CUser | null>;\n  updateUser(id: string, updates: Partial\u003CCreateUserInput>): Promise\u003CUser>;\n  deleteUser(id: string): Promise\u003Cvoid>;\n}\n\n\u002F\u002F Test file: user-service.test.ts\n\u002F\u002F Copilot uses the types to generate comprehensive tests\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\nimport { UserService } from '.\u002Fuser-service';\n\ndescribe('UserService', () => {\n  let service: UserService;\n\n  beforeEach(() => {\n    service = new UserService(\u002F* mocked deps *\u002F);\n  });\n\n  describe('createUser', () => {\n    \u002F\u002F Valid creation with all required fields\n    it('should create user with valid input', async () => {\n      const input = { name: 'John Doe', email: 'john@test.com', age: 25, role: 'user' as const };\n      const user = await service.createUser(input);\n      expect(user.name).toBe('John Doe');\n      expect(user.email).toBe('john@test.com');\n    });\n\n    \u002F\u002F Copilot generates boundary tests based on type comments\n    \u002F\u002F Name boundary: empty name\n    it('should reject empty name', async () => {\n      const input = { name: '', email: 'john@test.com', age: 25, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n\n    \u002F\u002F Name boundary: name exceeding 100 characters\n    it('should reject name over 100 characters', async () => {\n      const input = { name: 'a'.repeat(101), email: 'john@test.com', age: 25, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n\n    \u002F\u002F Age boundary: below minimum (18)\n    it('should reject age below 18', async () => {\n      const input = { name: 'John', email: 'john@test.com', age: 17, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n\n    \u002F\u002F Age boundary: at minimum (18)\n    it('should accept age at minimum 18', async () => {\n      const input = { name: 'John', email: 'john@test.com', age: 18, role: 'user' as const };\n      const user = await service.createUser(input);\n      expect(user.age).toBe(18);\n    });\n\n    \u002F\u002F Age boundary: above maximum (150)\n    it('should reject age above 150', async () => {\n      const input = { name: 'John', email: 'john@test.com', age: 151, role: 'user' as const };\n      await expect(service.createUser(input)).rejects.toThrow();\n    });\n  });\n});\n```\n\n## Copilot Chat Prompts for Testing\n\n```typescript\n\u002F\u002F Use these Copilot Chat slash commands and prompts:\n\n\u002F\u002F \u002Ftests - Generate tests for the selected code\n\u002F\u002F @workspace \u002Ftests - Generate tests considering workspace context\n\n\u002F\u002F Effective prompts for Copilot Chat:\n\n\u002F\u002F 1. \"Generate unit tests for UserService.createUser covering:\n\u002F\u002F     - valid input scenarios\n\u002F\u002F     - boundary values for name length\n\u002F\u002F     - invalid email formats\n\u002F\u002F     - age range validation\n\u002F\u002F     Use vitest with TypeScript\"\n\n\u002F\u002F 2. \"This test is failing with error: 'Expected 200, received 401'.\n\u002F\u002F     The API endpoint requires authentication.\n\u002F\u002F     Help me fix the test by adding proper auth headers.\"\n\n\u002F\u002F 3. \"Refactor these tests to use a test factory pattern:\n\u002F\u002F     - Extract user creation to a factory function\n\u002F\u002F     - Parameterize the test data\n\u002F\u002F     - Add beforeEach setup\"\n\n\u002F\u002F 4. \"Generate integration tests for the checkout flow:\n\u002F\u002F     1. Add item to cart\n\u002F\u002F     2. Apply discount code\n\u002F\u002F     3. Enter shipping info\n\u002F\u002F     4. Complete payment\n\u002F\u002F     Use Playwright with page object model\"\n\n\u002F\u002F 5. \"Convert this Jest test to Vitest:\n\u002F\u002F     - Replace jest.fn() with vi.fn()\n\u002F\u002F     - Replace jest.mock() with vi.mock()\n\u002F\u002F     - Update imports\"\n```\n\n## VS Code Settings for Copilot Testing\n\n```json\n{\n  \"github.copilot.enable\": {\n    \"*\": true,\n    \"yaml\": true,\n    \"markdown\": true\n  },\n  \"github.copilot.chat.testGeneration.instructions\": [\n    {\n      \"text\": \"Use vitest for all test files. Follow AAA pattern. Include edge cases.\"\n    }\n  ],\n  \"editor.inlineSuggest.enabled\": true,\n  \"github.copilot.chat.localeOverride\": \"en\"\n}\n```\n\n## Pattern 3: Mock-First Test Generation\n\n```typescript\n\u002F\u002F Start with mock setup - Copilot will generate tests that use these mocks\n\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\nimport { OrderService } from '.\u002Forder-service';\nimport { PaymentGateway } from '.\u002Fpayment-gateway';\nimport { InventoryService } from '.\u002Finventory-service';\nimport { EmailService } from '.\u002Femail-service';\n\n\u002F\u002F Mock all dependencies\nvi.mock('.\u002Fpayment-gateway');\nvi.mock('.\u002Finventory-service');\nvi.mock('.\u002Femail-service');\n\ndescribe('OrderService', () => {\n  let orderService: OrderService;\n  let mockPayment: vi.Mocked\u003CPaymentGateway>;\n  let mockInventory: vi.Mocked\u003CInventoryService>;\n  let mockEmail: vi.Mocked\u003CEmailService>;\n\n  beforeEach(() => {\n    mockPayment = new PaymentGateway() as vi.Mocked\u003CPaymentGateway>;\n    mockInventory = new InventoryService() as vi.Mocked\u003CInventoryService>;\n    mockEmail = new EmailService() as vi.Mocked\u003CEmailService>;\n\n    orderService = new OrderService(mockPayment, mockInventory, mockEmail);\n\n    \u002F\u002F Default mock returns\n    mockPayment.charge.mockResolvedValue({ success: true, transactionId: 'tx-123' });\n    mockInventory.checkStock.mockResolvedValue({ available: true, quantity: 10 });\n    mockEmail.send.mockResolvedValue(undefined);\n  });\n\n  \u002F\u002F Copilot will now generate tests using the established mocks:\n\n  it('should create order when payment and inventory are available', async () => {\n    const order = await orderService.createOrder({\n      items: [{ productId: 'p1', quantity: 2 }],\n      userId: 'u1',\n    });\n\n    expect(order.status).toBe('confirmed');\n    expect(mockPayment.charge).toHaveBeenCalledOnce();\n    expect(mockInventory.checkStock).toHaveBeenCalledWith('p1', 2);\n    expect(mockEmail.send).toHaveBeenCalledOnce();\n  });\n\n  it('should fail when payment is declined', async () => {\n    mockPayment.charge.mockResolvedValue({ success: false, error: 'Declined' });\n\n    await expect(\n      orderService.createOrder({ items: [{ productId: 'p1', quantity: 1 }], userId: 'u1' })\n    ).rejects.toThrow('Payment declined');\n  });\n\n  it('should fail when item is out of stock', async () => {\n    mockInventory.checkStock.mockResolvedValue({ available: false, quantity: 0 });\n\n    await expect(\n      orderService.createOrder({ items: [{ productId: 'p1', quantity: 1 }], userId: 'u1' })\n    ).rejects.toThrow('Out of stock');\n  });\n});\n```\n\n## Pattern 4: Copilot for Test Refactoring\n\n```typescript\n\u002F\u002F Refactoring workflow: select existing tests and ask Copilot to improve them\n\n\u002F\u002F Before: Repetitive test setup\ndescribe('UserAPI', () => {\n  it('should get user', async () => {\n    const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fusers\u002F1');\n    const data = await response.json();\n    expect(data.name).toBe('Alice');\n  });\n\n  it('should update user', async () => {\n    const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fusers\u002F1', {\n      method: 'PUT',\n      headers: { 'Content-Type': 'application\u002Fjson' },\n      body: JSON.stringify({ name: 'Bob' }),\n    });\n    const data = await response.json();\n    expect(data.name).toBe('Bob');\n  });\n});\n\n\u002F\u002F After: Ask Copilot \"Refactor to use a shared API client and beforeEach setup\"\ndescribe('UserAPI', () => {\n  let apiClient: TestApiClient;\n\n  beforeEach(() => {\n    apiClient = new TestApiClient('http:\u002F\u002Flocalhost:3000\u002Fapi');\n  });\n\n  it('should get user by ID', async () => {\n    const user = await apiClient.get('\u002Fusers\u002F1');\n    expect(user.name).toBe('Alice');\n    expect(user.id).toBe('1');\n  });\n\n  it('should update user name', async () => {\n    const user = await apiClient.put('\u002Fusers\u002F1', { name: 'Bob' });\n    expect(user.name).toBe('Bob');\n  });\n});\n```\n\n## Pattern 5: Copilot for E2E Test Generation\n\n```typescript\n\u002F\u002F Prompt pattern: Write a descriptive comment block, then let Copilot generate\n\n\u002F\u002F Checkout flow E2E test using Playwright\n\u002F\u002F Steps:\n\u002F\u002F 1. Navigate to product page\n\u002F\u002F 2. Add item to cart\n\u002F\u002F 3. Go to cart page\n\u002F\u002F 4. Proceed to checkout\n\u002F\u002F 5. Fill shipping information\n\u002F\u002F 6. Select payment method\n\u002F\u002F 7. Confirm order\n\u002F\u002F 8. Verify order confirmation page\nimport { test, expect } from '@playwright\u002Ftest';\n\ntest('complete checkout flow', async ({ page }) => {\n  \u002F\u002F Navigate to product page\n  await page.goto('\u002Fproducts\u002Fwireless-headphones');\n  await expect(page.getByRole('heading', { name: \u002Fwireless headphones\u002Fi })).toBeVisible();\n\n  \u002F\u002F Add item to cart\n  await page.getByRole('button', { name: 'Add to Cart' }).click();\n  await expect(page.getByText('Added to cart')).toBeVisible();\n\n  \u002F\u002F Go to cart page\n  await page.getByRole('link', { name: 'Cart' }).click();\n  await expect(page).toHaveURL(\u002F\\\u002Fcart\u002F);\n  await expect(page.getByText('Wireless Headphones')).toBeVisible();\n\n  \u002F\u002F Proceed to checkout\n  await page.getByRole('button', { name: 'Proceed to Checkout' }).click();\n  await expect(page).toHaveURL(\u002F\\\u002Fcheckout\u002F);\n\n  \u002F\u002F Fill shipping information\n  await page.getByLabel('Full Name').fill('John Doe');\n  await page.getByLabel('Address').fill('123 Test Street');\n  await page.getByLabel('City').fill('San Francisco');\n  await page.getByLabel('State').selectOption('CA');\n  await page.getByLabel('ZIP Code').fill('94105');\n\n  \u002F\u002F Select payment method\n  await page.getByLabel('Credit Card').check();\n  await page.getByLabel('Card Number').fill('4111111111111111');\n  await page.getByLabel('Expiry').fill('12\u002F28');\n  await page.getByLabel('CVC').fill('123');\n\n  \u002F\u002F Confirm order\n  await page.getByRole('button', { name: 'Place Order' }).click();\n\n  \u002F\u002F Verify order confirmation\n  await expect(page).toHaveURL(\u002F\\\u002Forder-confirmation\u002F);\n  await expect(page.getByText('Thank you for your order')).toBeVisible();\n  await expect(page.getByText('Order #')).toBeVisible();\n});\n```\n\n## Copilot Keyboard Shortcuts for Testing\n\nUse these shortcuts to accelerate test development with Copilot:\n\n- **Tab**: Accept the current inline suggestion\n- **Esc**: Dismiss the current suggestion\n- **Alt+]** \u002F **Option+]**: View next suggestion when multiple are available\n- **Alt+[** \u002F **Option+[**: View previous suggestion\n- **Ctrl+Enter**: Open Copilot completions panel with multiple suggestions\n- **Ctrl+I** \u002F **Cmd+I**: Open Copilot Chat inline\n- **Ctrl+Shift+I**: Open Copilot Chat panel\n\nFor testing workflows, the most productive pattern is to type a descriptive comment, wait for Copilot to suggest the test implementation, use Alt+] to cycle through alternatives, and Tab to accept the best suggestion. Then immediately run the test with the test runner to validate.\n\n## Pattern 6: Copilot for Error Handling Tests\n\n```typescript\n\u002F\u002F Comment-driven: generate error handling tests for a service\n\u002F\u002F Test that UserService handles all error cases:\n\u002F\u002F - Database connection errors\n\u002F\u002F - Validation errors for invalid email format\n\u002F\u002F - Duplicate email conflicts\n\u002F\u002F - Not found errors for missing users\n\u002F\u002F - Rate limit exceeded errors\n\u002F\u002F - Network timeout errors\nimport { describe, it, expect, vi, beforeEach } from 'vitest';\nimport { UserService } from '.\u002Fuser-service';\n\nvi.mock('.\u002Fdatabase');\nimport { db } from '.\u002Fdatabase';\n\ndescribe('UserService Error Handling', () => {\n  let service: UserService;\n\n  beforeEach(() => {\n    service = new UserService();\n    vi.clearAllMocks();\n  });\n\n  it('should throw DatabaseConnectionError when DB is unavailable', async () => {\n    vi.mocked(db.query).mockRejectedValueOnce(new Error('ECONNREFUSED'));\n    await expect(service.findById('1')).rejects.toThrow('Database connection failed');\n  });\n\n  it('should throw ValidationError for invalid email format', async () => {\n    await expect(\n      service.create({ name: 'Test', email: 'not-an-email', age: 25 })\n    ).rejects.toThrow('Invalid email format');\n  });\n\n  it('should throw ConflictError for duplicate email', async () => {\n    vi.mocked(db.insert).mockRejectedValueOnce(new Error('UNIQUE constraint'));\n    await expect(\n      service.create({ name: 'Test', email: 'exists@test.com', age: 25 })\n    ).rejects.toThrow('Email already exists');\n  });\n\n  it('should throw NotFoundError for missing user', async () => {\n    vi.mocked(db.query).mockResolvedValueOnce([]);\n    await expect(service.findById('missing')).rejects.toThrow('User not found');\n  });\n});\n```\n\n## Configuring Copilot for Testing Projects\n\n```json\n{\n  \"github.copilot.chat.testGeneration.instructions\": [\n    {\n      \"text\": \"Always use vitest. Follow AAA pattern. Include edge cases for null, undefined, empty values. Use vi.mock for module mocking. Use vi.fn for function mocking. Reset mocks in beforeEach.\"\n    }\n  ],\n  \"github.copilot.chat.codeGeneration.instructions\": [\n    {\n      \"text\": \"When generating test files, include all necessary imports at the top. Group tests in describe blocks. Use it() for individual tests. Include both positive and negative test cases.\"\n    }\n  ]\n}\n```\n\n## Best Practices\n\n1. **Write the first test manually, let Copilot continue** -- Establishing a pattern with one manually-written test gives Copilot the context to generate consistent follow-up tests.\n2. **Keep source and test files open side by side** -- Copilot uses open editor tabs as context. The source file being visible dramatically improves suggestion quality.\n3. **Use descriptive comments as specifications** -- A comment like \"should reject passwords shorter than 8 characters\" produces better suggestions than \"test short password\".\n4. **Accept and then refine** -- Copilot's first suggestion is rarely perfect but usually 70-80% correct. Accept it and fix the details manually.\n5. **Use Copilot Chat for complex test scenarios** -- Multi-step tests, integration tests, and test refactoring benefit from Chat's conversational context.\n6. **Configure custom instructions for your project** -- Create .github\u002Fcopilot\u002Finstructions.md with your testing conventions so Copilot follows project standards.\n7. **Review all generated assertions** -- Copilot may generate assertions that are technically valid but test the wrong behavior. Verify every expect statement.\n8. **Use type annotations to improve suggestions** -- Strong TypeScript types give Copilot better context for generating boundary tests and error cases.\n9. **Leverage slash commands** -- Use \u002Ftests, \u002Ffix, and \u002Fexplain in Copilot Chat for specific testing tasks.\n10. **Create a test patterns reference file** -- Keep a file with exemplary test patterns open when generating tests. Copilot will reference it for style consistency.\n\n## Anti-Patterns\n\n1. **Blindly accepting all suggestions** -- Copilot generates plausible but potentially incorrect tests. Every suggestion must be reviewed by a human.\n2. **Not providing context** -- Generating tests with only the test file open (no source code) produces generic, potentially incorrect tests.\n3. **Over-relying on Copilot for complex logic** -- Copilot excels at pattern continuation but struggles with complex business logic verification. Write critical assertions manually.\n4. **Ignoring test quality** -- Generated tests may use weak assertions (toBeDefined instead of specific values), skip error cases, or test implementation details.\n5. **Not establishing patterns first** -- Without a pattern to follow, Copilot generates inconsistent test styles across the codebase.\n6. **Using Copilot for security tests** -- Security testing requires domain expertise. Copilot may miss critical attack vectors or generate false security checks.\n7. **Generating all tests at once** -- Generate tests incrementally, validate each batch, then continue. Bulk generation without validation produces unreliable suites.\n8. **Not using custom instructions** -- Without project-specific instructions, Copilot uses generic patterns that may not match your codebase conventions.\n9. **Trusting generated mock implementations** -- Copilot creates mocks that look correct but may not accurately represent real dependency behavior. Verify mock contracts.\n10. **Not testing the generated tests** -- Always run generated tests immediately. A test that does not compile or always passes provides zero value.\n\n## Copilot Workspace for Test Planning\n\nGitHub Copilot Workspace extends Copilot beyond code generation into test planning. When reviewing an issue or feature request, Copilot Workspace can analyze the proposed changes, suggest test scenarios that should be covered, generate test skeletons for each scenario, and create a plan for the testing approach.\n\nThis is particularly useful during sprint planning when the team needs to estimate testing effort. Copilot Workspace can analyze the proposed feature, suggest the types of tests needed (unit, integration, E2E), estimate the number of test cases, and provide skeleton implementations that developers can complete.\n\n## Copilot CLI for Test Execution\n\nGitHub Copilot CLI assists with test-related command-line tasks. Instead of remembering exact command syntax, describe what you want to do in natural language. For example, ask Copilot to explain how to run tests matching a specific pattern, run tests with coverage and generate a report, watch tests for a specific file, or debug a failing test by running it in isolation.\n\nCopilot CLI translates your natural language request into the correct command for your test runner, whether it is vitest, jest, playwright, or another tool.\n\n## Integration with GitHub Actions\n\nCopilot can generate GitHub Actions workflows for testing. Describe your CI requirements and Copilot produces a complete workflow file with dependency caching, parallel test execution, coverage reporting, and artifact upload.\n\nFor testing-specific workflows, Copilot generates appropriate job configurations including browser installation for E2E tests, database setup for integration tests, and environment variable configuration for different deployment targets.\n",{"name":5,"tags":24,"agents":34,"author":46,"domains":47,"license":15,"version":52,"languages":53,"frameworks":58,"description":7,"testingTypes":64},[25,26,27,28,29,30,31,32,33],"github-copilot","copilot-chat","ai-pair-programming","test-generation","code-completion","prompt-engineering","inline-suggestions","debugging","vscode",[35,36,25,37,38,39,40,41,42,43,44,45],"claude-code","cursor","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","thetestingacademy",[48,49,50,51],"web","backend","api","mobile","1.0.0",[54,55,56,57],"typescript","javascript","python","java",[59,60,61,62,63],"vitest","jest","playwright","cypress","pytest",[65,66,67,50],"unit","integration","e2e","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fcopilot-testing-patterns","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m","https:\u002F\u002Fid-preview--d5bef06d-6c9e-4563-a3d4-a855b9d61610.lovable.app\u002F","Eu sou Antonio B. B. Ndombe \r\nEu sou um Pesquisador e desenvolvedor de sistema autonomia cognitivos, fundador de sistemas ODCs ( organismos digital conscientes)","2026-11-04 06:53:39",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"GitHub Copilot Testing Patterns\"",{"tool":82,"command":83},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"GitHub Copilot Testing Patterns\"",{"tool":85,"command":86},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"GitHub Copilot Testing Patterns\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fcopilot-testing-patterns\u002FSKILL.md",true,[],[91,99,106,113,120,127],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DASC6FSCJP49JZBSK0NY1Z","nemoclaw-user-reference","Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-reference\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DAS5S79VK33XFGVAM2TFWF","nemoclaw-user-overview","Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-overview\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7DAS0PQEMET5MNGZ1ABSZVS","nemoclaw-user-monitor-sandbox","Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-monitor-sandbox\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7DARQYGF7E9A69VH6S3CGN9","nemoclaw-user-manage-sandboxes","Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-sandboxes\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7DARH8BRTG51TRCAB7YWDJ4","nemoclaw-user-manage-policy","Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-policy\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7DARAT62M2VR37590VCZ5NS","nemoclaw-user-get-started","Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[]]