[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70J3RXE1B51C7A67TCWPD9B":3,"skill-same:01M70J3RXE1B51C7A67TCWPD9B":84},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M70J3RXE1B51C7A67TCWPD9B","test-strategy-design",null,"Test pyramid strategy, test design patterns, coverage analysis, and quality gate configuration. Use when designing test strategies, improving coverage, setting up automation, or defining quality gates. Covers unit, integration, and E2E testing across frameworks.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Ftest-strategy-design\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"design","test strategy","strategy","test","test strategy design","e2e","frameworks","quality gate","patterns","coverage analysis","strategies","across","analysis","when","up","testing","test strategies","design patterns","unit","coverage","2026-11-10 10:12:30",false,"---\nname: test-strategy-design\ndescription: Test pyramid strategy, test design patterns, coverage analysis, and quality gate configuration. Use when designing test strategies, improving coverage, setting up automation, or defining quality gates. Covers unit, integration, and E2E testing across frameworks.\n---\n\n# Test Strategy Design\n\nSystematic patterns for designing comprehensive test strategies that balance coverage, speed, and maintainability.\n\n## When to Activate\n\n- Designing test strategy for new projects\n- Improving existing test coverage\n- Setting up test automation frameworks\n- Configuring CI\u002FCD quality gates\n- Analyzing test gaps and priorities\n- Establishing testing standards for teams\n\n## The Test Pyramid\n\nThe test pyramid guides the distribution of testing effort:\n\n```\n                 ┌─────────┐\n                 │   E2E   │  ~10% - Critical user journeys\n                 │ Tests   │  Slow, expensive, high confidence\n                 ├─────────┤\n                 │ Integr- │  ~20% - Component interactions\n                 │  ation  │  Medium speed, real dependencies\n                 ├─────────┤\n                 │  Unit   │  ~70% - Business logic\n                 │  Tests  │  Fast, isolated, cheap\n                 └─────────┘\n```\n\n### Layer Characteristics\n\n| Layer | Speed | Isolation | Confidence | Maintenance |\n|-------|-------|-----------|------------|-------------|\n| Unit | \u003C 10ms | Complete | Low per test | Low |\n| Integration | \u003C 1s | Partial | Medium | Medium |\n| E2E | \u003C 30s | None | High | High |\n\n### When to Test at Each Layer\n\n**Unit Tests** - Test here when:\n- Pure business logic\n- Algorithmic code\n- Data transformations\n- Validation rules\n- Edge cases and boundaries\n\n**Integration Tests** - Test here when:\n- Database interactions\n- API contracts\n- Service communication\n- File system operations\n- Cache behavior\n\n**E2E Tests** - Test here when:\n- Critical user journeys\n- Cross-system workflows\n- Authentication flows\n- Payment processes\n- Smoke tests for deployments\n\n## Test Design Patterns\n\n### Unit Test Patterns\n\n#### Arrange-Act-Assert (AAA)\n\n```\n\u002F\u002F Arrange: Set up test data and dependencies\nconst user = createUser({ email: 'test@example.com' });\nconst validator = new EmailValidator();\n\n\u002F\u002F Act: Execute the behavior under test\nconst result = validator.validate(user.email);\n\n\u002F\u002F Assert: Verify the expected outcome\nexpect(result.isValid).toBe(true);\n```\n\n#### One Assertion Per Test\n\nFocus each test on a single behavior:\n\n```\n\u002F\u002F Bad: Multiple unrelated assertions\ntest('user validation', () => {\n  expect(user.isValid()).toBe(true);\n  expect(user.email).toContain('@');\n  expect(user.createdAt).toBeDefined();\n});\n\n\u002F\u002F Good: Separate tests for each behavior\ntest('validates user with proper email', () => {\n  expect(user.isValid()).toBe(true);\n});\n\ntest('email contains @ symbol', () => {\n  expect(user.email).toContain('@');\n});\n```\n\n#### Descriptive Test Names\n\nTest names should describe the expected behavior:\n\n```\n\u002F\u002F Bad\ntest('email test', () => { ... });\n\n\u002F\u002F Good\ntest('rejects email without domain', () => { ... });\ntest('accepts email with subdomain', () => { ... });\ntest('trims whitespace from email input', () => { ... });\n```\n\n#### Test Data Builders\n\nCreate readable test data:\n\n```\n\u002F\u002F Builder pattern for test data\nconst user = UserBuilder.create()\n  .withEmail('test@example.com')\n  .withRole('admin')\n  .withActiveSubscription()\n  .build();\n```\n\n### Integration Test Patterns\n\n#### Test Through Public Interfaces\n\n```\n\u002F\u002F Bad: Testing internal implementation\ntest('repository uses correct SQL', () => {\n  const sql = userRepo.buildQuery();\n  expect(sql).toContain('SELECT * FROM users');\n});\n\n\u002F\u002F Good: Testing behavior through public API\ntest('finds users by email domain', async () => {\n  await userRepo.save(createUser({ email: 'a@corp.com' }));\n  await userRepo.save(createUser({ email: 'b@corp.com' }));\n\n  const users = await userRepo.findByDomain('corp.com');\n\n  expect(users).toHaveLength(2);\n});\n```\n\n#### Use Real Dependencies Where Practical\n\n```\n\u002F\u002F Prefer real database for repository tests\nbeforeAll(async () => {\n  testDb = await createTestDatabase();\n});\n\nafterEach(async () => {\n  await testDb.truncateAll();\n});\n\n\u002F\u002F Mock only external services\njest.mock('.\u002FpaymentGateway', () => ({\n  charge: jest.fn().mockResolvedValue({ success: true })\n}));\n```\n\n#### Contract Testing\n\nVerify API contracts between services:\n\n```\n\u002F\u002F Consumer contract\ndescribe('User API Contract', () => {\n  test('GET \u002Fusers\u002F:id returns user shape', async () => {\n    const response = await api.get('\u002Fusers\u002F123');\n\n    expect(response).toMatchSchema({\n      id: expect.any(String),\n      email: expect.any(String),\n      createdAt: expect.any(String),\n    });\n  });\n});\n```\n\n### E2E Test Patterns\n\n#### Critical Path Focus\n\nOnly test the most important user journeys:\n\n```\n\u002F\u002F Priority 1: Revenue-critical paths\ntest('complete purchase flow', async () => {\n  await page.addToCart(product);\n  await page.checkout();\n  await page.enterPayment(validCard);\n  await page.confirmOrder();\n\n  await expect(page.orderConfirmation).toBeVisible();\n});\n\n\u002F\u002F Priority 2: Core functionality\ntest('user registration and login', async () => {\n  await page.register(newUser);\n  await page.login(newUser);\n\n  await expect(page.dashboard).toBeVisible();\n});\n```\n\n#### Page Object Pattern\n\nEncapsulate page interactions:\n\n```\nclass CheckoutPage {\n  constructor(page) {\n    this.page = page;\n  }\n\n  async enterShippingAddress(address) {\n    await this.page.fill('#street', address.street);\n    await this.page.fill('#city', address.city);\n    await this.page.fill('#zip', address.zip);\n  }\n\n  async submitOrder() {\n    await this.page.click('[data-testid=\"submit-order\"]');\n    await this.page.waitForURL('**\u002Fconfirmation');\n  }\n}\n```\n\n#### Resilient Selectors\n\nUse stable selectors that survive UI changes:\n\n```\n\u002F\u002F Fragile: Based on CSS\u002Fposition\nawait page.click('.btn-primary');\nawait page.click('div > div:nth-child(2) > button');\n\n\u002F\u002F Stable: Based on test IDs or roles\nawait page.click('[data-testid=\"submit-button\"]');\nawait page.getByRole('button', { name: 'Submit' });\n```\n\n## Coverage Strategy\n\n### Coverage Types\n\n| Type | Measures | Target |\n|------|----------|--------|\n| Line | Lines executed | 80% |\n| Branch | Decision paths taken | 75% |\n| Function | Functions called | 90% |\n| Statement | Statements executed | 80% |\n\n### Coverage Prioritization\n\nFocus coverage on high-risk areas:\n\n```\nHigh Priority (100% coverage):\n├── Payment processing\n├── Authentication\u002FAuthorization\n├── Data validation\n├── Business rule enforcement\n└── Security-sensitive code\n\nMedium Priority (80% coverage):\n├── Core business logic\n├── API endpoints\n├── Data transformations\n└── Error handling\n\nLower Priority (60% coverage):\n├── UI components\n├── Configuration\n├── Logging\u002FMonitoring\n└── Admin features\n```\n\n### Meaningful Coverage\n\nCoverage quantity vs quality:\n\n```\n\u002F\u002F 100% coverage, low value\ntest('getter returns value', () => {\n  user.name = 'John';\n  expect(user.name).toBe('John');\n});\n\n\u002F\u002F 80% coverage, high value\ntest('rejects order when inventory insufficient', () => {\n  const inventory = createInventory({ quantity: 5 });\n  const order = createOrder({ quantity: 10 });\n\n  expect(() => processOrder(order, inventory))\n    .toThrow('Insufficient inventory');\n});\n```\n\n## Quality Gates\n\n### Gate Configuration\n\n| Gate | Threshold | Enforcement |\n|------|-----------|-------------|\n| Unit Tests | 100% pass | Block merge |\n| Integration Tests | 100% pass | Block merge |\n| E2E Tests | 100% pass | Block deploy |\n| Line Coverage | ≥ 80% | Block merge |\n| Branch Coverage | ≥ 75% | Block merge |\n| New Code Coverage | ≥ 90% | Warn |\n| Test Duration | \u003C 10 min | Warn |\n\n### Flaky Test Management\n\n```\nFlaky Test Protocol:\n1. DETECT: Track test stability over time\n2. QUARANTINE: Move flaky tests to separate suite\n3. FIX: Prioritize fixing within 1 week\n4. REINTEGRATE: Return to main suite after 10 consecutive passes\n```\n\n### Test Performance Budgets\n\n| Test Type | Target Duration | Action if Exceeded |\n|-----------|-----------------|-------------------|\n| Single Unit Test | \u003C 10ms | Investigate |\n| Unit Suite | \u003C 30s | Parallelize |\n| Single Integration | \u003C 1s | Review setup\u002Fteardown |\n| Integration Suite | \u003C 2 min | Parallelize |\n| Single E2E | \u003C 30s | Optimize waits |\n| E2E Suite | \u003C 10 min | Reduce scope |\n\n## Test Organization\n\n### File Structure\n\n```\nsrc\u002F\n├── user\u002F\n│   ├── User.ts\n│   ├── User.test.ts           # Unit tests co-located\n│   ├── UserRepository.ts\n│   └── UserRepository.test.ts\n├── order\u002F\n│   ├── Order.ts\n│   └── Order.test.ts\ntests\u002F\n├── integration\u002F\n│   ├── api\u002F\n│   │   └── users.test.ts      # API integration tests\n│   └── database\u002F\n│       └── repositories.test.ts\n└── e2e\u002F\n    ├── checkout.spec.ts       # E2E tests by journey\n    └── registration.spec.ts\n```\n\n### Test Naming Conventions\n\n```\n# Unit tests: [unit].test.ts\nUser.test.ts\nOrderCalculator.test.ts\n\n# Integration tests: [feature].integration.test.ts\nusers.integration.test.ts\npayment-gateway.integration.test.ts\n\n# E2E tests: [journey].e2e.ts or [journey].spec.ts\ncheckout.e2e.ts\nuser-onboarding.spec.ts\n```\n\n## Test Data Management\n\n### Test Data Principles\n\n1. **Isolation**: Each test manages its own data\n2. **Cleanup**: Tests clean up after themselves\n3. **Determinism**: Same test, same data, same result\n4. **Minimal**: Only create data needed for the test\n\n### Factories and Fixtures\n\n```\n\u002F\u002F Factory: Dynamic test data\nconst createUser = (overrides = {}) => ({\n  id: faker.string.uuid(),\n  email: faker.internet.email(),\n  name: faker.person.fullName(),\n  ...overrides\n});\n\n\u002F\u002F Fixture: Static reference data\nconst ADMIN_USER = {\n  id: 'admin-001',\n  email: 'admin@test.com',\n  role: 'admin'\n};\n```\n\n### Database Test Patterns\n\n```\n\u002F\u002F Transaction rollback pattern\nbeforeEach(async () => {\n  transaction = await db.beginTransaction();\n});\n\nafterEach(async () => {\n  await transaction.rollback();\n});\n\n\u002F\u002F Truncate pattern (slower but more isolated)\nafterEach(async () => {\n  await db.truncateAll();\n});\n```\n\n## CI\u002FCD Integration\n\n### Pipeline Configuration\n\n```yaml\ntest:\n  stages:\n    - lint-and-typecheck    # Fast feedback first\n    - unit-tests            # Parallel execution\n    - integration-tests     # With test database\n    - e2e-tests             # Against staging environment\n\n  parallelization:\n    unit: 4 workers\n    integration: 2 workers\n    e2e: 1 worker (sequential for stability)\n\n  artifacts:\n    - coverage reports\n    - test results (JUnit XML)\n    - E2E screenshots\u002Fvideos on failure\n```\n\n### Failure Handling\n\n```\nOn Test Failure:\n1. Capture: Screenshots, logs, database state\n2. Report: Notify team channel\n3. Block: Prevent merge\u002Fdeploy\n4. Retry: Once for E2E (flaky detection)\n```\n\n## Best Practices\n\n### Do\n\n- Test behavior, not implementation\n- Keep tests independent and isolated\n- Use meaningful, descriptive test names\n- Maintain test code like production code\n- Run tests frequently during development\n- Fix flaky tests immediately\n\n### Avoid\n\n- Testing private methods directly\n- Mocking everything (use real dependencies where practical)\n- Ignoring slow tests (fix the root cause)\n- Writing tests after bugs (write them before)\n- Sharing state between tests\n- Over-relying on E2E tests\n\n## References\n\n- [Test Pattern Examples](examples\u002Ftest-patterns.md) - Code examples for each pattern\n- [Framework-Specific Guides](reference.md) - Jest, Pytest, Go testing patterns\n","# Test Strategy Design\n\nSystematic patterns for designing comprehensive test strategies that balance coverage, speed, and maintainability.\n\n## When to Activate\n\n- Designing test strategy for new projects\n- Improving existing test coverage\n- Setting up test automation frameworks\n- Configuring CI\u002FCD quality gates\n- Analyzing test gaps and priorities\n- Establishing testing standards for teams\n\n## The Test Pyramid\n\nThe test pyramid guides the distribution of testing effort:\n\n```\n                 ┌─────────┐\n                 │   E2E   │  ~10% - Critical user journeys\n                 │ Tests   │  Slow, expensive, high confidence\n                 ├─────────┤\n                 │ Integr- │  ~20% - Component interactions\n                 │  ation  │  Medium speed, real dependencies\n                 ├─────────┤\n                 │  Unit   │  ~70% - Business logic\n                 │  Tests  │  Fast, isolated, cheap\n                 └─────────┘\n```\n\n### Layer Characteristics\n\n| Layer | Speed | Isolation | Confidence | Maintenance |\n|-------|-------|-----------|------------|-------------|\n| Unit | \u003C 10ms | Complete | Low per test | Low |\n| Integration | \u003C 1s | Partial | Medium | Medium |\n| E2E | \u003C 30s | None | High | High |\n\n### When to Test at Each Layer\n\n**Unit Tests** - Test here when:\n- Pure business logic\n- Algorithmic code\n- Data transformations\n- Validation rules\n- Edge cases and boundaries\n\n**Integration Tests** - Test here when:\n- Database interactions\n- API contracts\n- Service communication\n- File system operations\n- Cache behavior\n\n**E2E Tests** - Test here when:\n- Critical user journeys\n- Cross-system workflows\n- Authentication flows\n- Payment processes\n- Smoke tests for deployments\n\n## Test Design Patterns\n\n### Unit Test Patterns\n\n#### Arrange-Act-Assert (AAA)\n\n```\n\u002F\u002F Arrange: Set up test data and dependencies\nconst user = createUser({ email: 'test@example.com' });\nconst validator = new EmailValidator();\n\n\u002F\u002F Act: Execute the behavior under test\nconst result = validator.validate(user.email);\n\n\u002F\u002F Assert: Verify the expected outcome\nexpect(result.isValid).toBe(true);\n```\n\n#### One Assertion Per Test\n\nFocus each test on a single behavior:\n\n```\n\u002F\u002F Bad: Multiple unrelated assertions\ntest('user validation', () => {\n  expect(user.isValid()).toBe(true);\n  expect(user.email).toContain('@');\n  expect(user.createdAt).toBeDefined();\n});\n\n\u002F\u002F Good: Separate tests for each behavior\ntest('validates user with proper email', () => {\n  expect(user.isValid()).toBe(true);\n});\n\ntest('email contains @ symbol', () => {\n  expect(user.email).toContain('@');\n});\n```\n\n#### Descriptive Test Names\n\nTest names should describe the expected behavior:\n\n```\n\u002F\u002F Bad\ntest('email test', () => { ... });\n\n\u002F\u002F Good\ntest('rejects email without domain', () => { ... });\ntest('accepts email with subdomain', () => { ... });\ntest('trims whitespace from email input', () => { ... });\n```\n\n#### Test Data Builders\n\nCreate readable test data:\n\n```\n\u002F\u002F Builder pattern for test data\nconst user = UserBuilder.create()\n  .withEmail('test@example.com')\n  .withRole('admin')\n  .withActiveSubscription()\n  .build();\n```\n\n### Integration Test Patterns\n\n#### Test Through Public Interfaces\n\n```\n\u002F\u002F Bad: Testing internal implementation\ntest('repository uses correct SQL', () => {\n  const sql = userRepo.buildQuery();\n  expect(sql).toContain('SELECT * FROM users');\n});\n\n\u002F\u002F Good: Testing behavior through public API\ntest('finds users by email domain', async () => {\n  await userRepo.save(createUser({ email: 'a@corp.com' }));\n  await userRepo.save(createUser({ email: 'b@corp.com' }));\n\n  const users = await userRepo.findByDomain('corp.com');\n\n  expect(users).toHaveLength(2);\n});\n```\n\n#### Use Real Dependencies Where Practical\n\n```\n\u002F\u002F Prefer real database for repository tests\nbeforeAll(async () => {\n  testDb = await createTestDatabase();\n});\n\nafterEach(async () => {\n  await testDb.truncateAll();\n});\n\n\u002F\u002F Mock only external services\njest.mock('.\u002FpaymentGateway', () => ({\n  charge: jest.fn().mockResolvedValue({ success: true })\n}));\n```\n\n#### Contract Testing\n\nVerify API contracts between services:\n\n```\n\u002F\u002F Consumer contract\ndescribe('User API Contract', () => {\n  test('GET \u002Fusers\u002F:id returns user shape', async () => {\n    const response = await api.get('\u002Fusers\u002F123');\n\n    expect(response).toMatchSchema({\n      id: expect.any(String),\n      email: expect.any(String),\n      createdAt: expect.any(String),\n    });\n  });\n});\n```\n\n### E2E Test Patterns\n\n#### Critical Path Focus\n\nOnly test the most important user journeys:\n\n```\n\u002F\u002F Priority 1: Revenue-critical paths\ntest('complete purchase flow', async () => {\n  await page.addToCart(product);\n  await page.checkout();\n  await page.enterPayment(validCard);\n  await page.confirmOrder();\n\n  await expect(page.orderConfirmation).toBeVisible();\n});\n\n\u002F\u002F Priority 2: Core functionality\ntest('user registration and login', async () => {\n  await page.register(newUser);\n  await page.login(newUser);\n\n  await expect(page.dashboard).toBeVisible();\n});\n```\n\n#### Page Object Pattern\n\nEncapsulate page interactions:\n\n```\nclass CheckoutPage {\n  constructor(page) {\n    this.page = page;\n  }\n\n  async enterShippingAddress(address) {\n    await this.page.fill('#street', address.street);\n    await this.page.fill('#city', address.city);\n    await this.page.fill('#zip', address.zip);\n  }\n\n  async submitOrder() {\n    await this.page.click('[data-testid=\"submit-order\"]');\n    await this.page.waitForURL('**\u002Fconfirmation');\n  }\n}\n```\n\n#### Resilient Selectors\n\nUse stable selectors that survive UI changes:\n\n```\n\u002F\u002F Fragile: Based on CSS\u002Fposition\nawait page.click('.btn-primary');\nawait page.click('div > div:nth-child(2) > button');\n\n\u002F\u002F Stable: Based on test IDs or roles\nawait page.click('[data-testid=\"submit-button\"]');\nawait page.getByRole('button', { name: 'Submit' });\n```\n\n## Coverage Strategy\n\n### Coverage Types\n\n| Type | Measures | Target |\n|------|----------|--------|\n| Line | Lines executed | 80% |\n| Branch | Decision paths taken | 75% |\n| Function | Functions called | 90% |\n| Statement | Statements executed | 80% |\n\n### Coverage Prioritization\n\nFocus coverage on high-risk areas:\n\n```\nHigh Priority (100% coverage):\n├── Payment processing\n├── Authentication\u002FAuthorization\n├── Data validation\n├── Business rule enforcement\n└── Security-sensitive code\n\nMedium Priority (80% coverage):\n├── Core business logic\n├── API endpoints\n├── Data transformations\n└── Error handling\n\nLower Priority (60% coverage):\n├── UI components\n├── Configuration\n├── Logging\u002FMonitoring\n└── Admin features\n```\n\n### Meaningful Coverage\n\nCoverage quantity vs quality:\n\n```\n\u002F\u002F 100% coverage, low value\ntest('getter returns value', () => {\n  user.name = 'John';\n  expect(user.name).toBe('John');\n});\n\n\u002F\u002F 80% coverage, high value\ntest('rejects order when inventory insufficient', () => {\n  const inventory = createInventory({ quantity: 5 });\n  const order = createOrder({ quantity: 10 });\n\n  expect(() => processOrder(order, inventory))\n    .toThrow('Insufficient inventory');\n});\n```\n\n## Quality Gates\n\n### Gate Configuration\n\n| Gate | Threshold | Enforcement |\n|------|-----------|-------------|\n| Unit Tests | 100% pass | Block merge |\n| Integration Tests | 100% pass | Block merge |\n| E2E Tests | 100% pass | Block deploy |\n| Line Coverage | ≥ 80% | Block merge |\n| Branch Coverage | ≥ 75% | Block merge |\n| New Code Coverage | ≥ 90% | Warn |\n| Test Duration | \u003C 10 min | Warn |\n\n### Flaky Test Management\n\n```\nFlaky Test Protocol:\n1. DETECT: Track test stability over time\n2. QUARANTINE: Move flaky tests to separate suite\n3. FIX: Prioritize fixing within 1 week\n4. REINTEGRATE: Return to main suite after 10 consecutive passes\n```\n\n### Test Performance Budgets\n\n| Test Type | Target Duration | Action if Exceeded |\n|-----------|-----------------|-------------------|\n| Single Unit Test | \u003C 10ms | Investigate |\n| Unit Suite | \u003C 30s | Parallelize |\n| Single Integration | \u003C 1s | Review setup\u002Fteardown |\n| Integration Suite | \u003C 2 min | Parallelize |\n| Single E2E | \u003C 30s | Optimize waits |\n| E2E Suite | \u003C 10 min | Reduce scope |\n\n## Test Organization\n\n### File Structure\n\n```\nsrc\u002F\n├── user\u002F\n│   ├── User.ts\n│   ├── User.test.ts           # Unit tests co-located\n│   ├── UserRepository.ts\n│   └── UserRepository.test.ts\n├── order\u002F\n│   ├── Order.ts\n│   └── Order.test.ts\ntests\u002F\n├── integration\u002F\n│   ├── api\u002F\n│   │   └── users.test.ts      # API integration tests\n│   └── database\u002F\n│       └── repositories.test.ts\n└── e2e\u002F\n    ├── checkout.spec.ts       # E2E tests by journey\n    └── registration.spec.ts\n```\n\n### Test Naming Conventions\n\n```\n# Unit tests: [unit].test.ts\nUser.test.ts\nOrderCalculator.test.ts\n\n# Integration tests: [feature].integration.test.ts\nusers.integration.test.ts\npayment-gateway.integration.test.ts\n\n# E2E tests: [journey].e2e.ts or [journey].spec.ts\ncheckout.e2e.ts\nuser-onboarding.spec.ts\n```\n\n## Test Data Management\n\n### Test Data Principles\n\n1. **Isolation**: Each test manages its own data\n2. **Cleanup**: Tests clean up after themselves\n3. **Determinism**: Same test, same data, same result\n4. **Minimal**: Only create data needed for the test\n\n### Factories and Fixtures\n\n```\n\u002F\u002F Factory: Dynamic test data\nconst createUser = (overrides = {}) => ({\n  id: faker.string.uuid(),\n  email: faker.internet.email(),\n  name: faker.person.fullName(),\n  ...overrides\n});\n\n\u002F\u002F Fixture: Static reference data\nconst ADMIN_USER = {\n  id: 'admin-001',\n  email: 'admin@test.com',\n  role: 'admin'\n};\n```\n\n### Database Test Patterns\n\n```\n\u002F\u002F Transaction rollback pattern\nbeforeEach(async () => {\n  transaction = await db.beginTransaction();\n});\n\nafterEach(async () => {\n  await transaction.rollback();\n});\n\n\u002F\u002F Truncate pattern (slower but more isolated)\nafterEach(async () => {\n  await db.truncateAll();\n});\n```\n\n## CI\u002FCD Integration\n\n### Pipeline Configuration\n\n```yaml\ntest:\n  stages:\n    - lint-and-typecheck    # Fast feedback first\n    - unit-tests            # Parallel execution\n    - integration-tests     # With test database\n    - e2e-tests             # Against staging environment\n\n  parallelization:\n    unit: 4 workers\n    integration: 2 workers\n    e2e: 1 worker (sequential for stability)\n\n  artifacts:\n    - coverage reports\n    - test results (JUnit XML)\n    - E2E screenshots\u002Fvideos on failure\n```\n\n### Failure Handling\n\n```\nOn Test Failure:\n1. Capture: Screenshots, logs, database state\n2. Report: Notify team channel\n3. Block: Prevent merge\u002Fdeploy\n4. Retry: Once for E2E (flaky detection)\n```\n\n## Best Practices\n\n### Do\n\n- Test behavior, not implementation\n- Keep tests independent and isolated\n- Use meaningful, descriptive test names\n- Maintain test code like production code\n- Run tests frequently during development\n- Fix flaky tests immediately\n\n### Avoid\n\n- Testing private methods directly\n- Mocking everything (use real dependencies where practical)\n- Ignoring slow tests (fix the root cause)\n- Writing tests after bugs (write them before)\n- Sharing state between tests\n- Over-relying on E2E tests\n\n## References\n\n- [Test Pattern Examples](examples\u002Ftest-patterns.md) - Code examples for each pattern\n- [Framework-Specific Guides](reference.md) - Jest, Pytest, Go testing patterns\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Ftest-strategy-design",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill test-strategy-design",{"tool":76,"command":77},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill test-strategy-design",{"tool":79,"command":80},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill test-strategy-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fquality\u002Ftest-strategy-design\u002FSKILL.md",true,[],[85,94,102,110,118,126],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":93},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":93},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":93},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":93},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":93},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]