[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78EE7P0TFMM30DDX8CRCAFB":3,"skill-same:01M78EE7P0TFMM30DDX8CRCAFB":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M78EE7P0TFMM30DDX8CRCAFB","testing-strategy",null,"Testing philosophy and strategy. Use this when deciding what to test, naming tests, or identifying corner cases.","aydabd\u002Fcacad","aydabd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F88633794?v=4","01M7592YHMQK95Z2DAJAPR4H6J","Aydina","01M78EAXTACH1JW62CWSMS92VZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing-strategy\ndescription: >\n  Testing philosophy and strategy. Use this when deciding what to test,\n  naming tests, or identifying corner cases.\n---\n\n# Skill: Testing Strategy\n\n## Testing Mindset\n\n- **Think like an adversary** — imagine how the code could break and test those paths.\n- **Value over coverage** — a test that proves real behavior beats a metric-inflating test.\n  Never write a test that cannot fail in a meaningful way.\n- **Readable by anyone** — test names and body must tell a complete story. A failing test\n  must explain the problem without requiring a debugger.\n\n## When to Add a Test\n\nAdd a test only when it satisfies at least ONE of:\n\n1. It catches a real bug that could reach production.\n2. It documents a non-obvious contract (e.g. \"returns empty list, never null\").\n3. It guards a regression that has already occurred.\n4. It validates the interaction between two real components.\n\n**Do NOT add tests for:**\n\n- Trivial getters\u002Fsetters with no logic.\n- Behaviour already fully covered by an existing test.\n- Happy-path-only tests when edge cases exist and are untested.\n- Tests that always pass regardless of implementation.\n\n## Test Case Naming\n\nUse the format `TestUnit_Scenario_ExpectedOutcome`:\n\n```text\nTestParseConfig_MissingRequiredField_ReturnsError\nTestParseConfig_ValidInput_ReturnsParsedResult\n```\n\nSub-tests use plain, readable English:\n\n```text\n\"missing required field returns error\"\n\"valid input with 3 items succeeds\"\n```\n\n## Anatomy of a Good Test\n\n1. **Arrange** — set up inputs and dependencies clearly; avoid hidden shared state.\n2. **Act** — single call to the unit under test.\n3. **Assert** — check the outcome and produce a message that explains the failure.\n\nKeep each test focused on **one behaviour**. When multiple scenarios exist, use\ntable rows rather than separate functions.\n\n## Corner Cases Checklist\n\nBefore marking a feature tested, ask:\n\n- What happens with a nil\u002Fnull\u002Fzero\u002Fempty input?\n- What happens at the boundary (first item, last item, exactly at a limit)?\n- What happens when a dependency fails halfway through?\n- What happens when the same operation runs concurrently?\n- What happens with the largest valid input?\n- What happens when required configuration is missing?\n","# Skill: Testing Strategy\n\n## Testing Mindset\n\n- **Think like an adversary** — imagine how the code could break and test those paths.\n- **Value over coverage** — a test that proves real behavior beats a metric-inflating test.\n  Never write a test that cannot fail in a meaningful way.\n- **Readable by anyone** — test names and body must tell a complete story. A failing test\n  must explain the problem without requiring a debugger.\n\n## When to Add a Test\n\nAdd a test only when it satisfies at least ONE of:\n\n1. It catches a real bug that could reach production.\n2. It documents a non-obvious contract (e.g. \"returns empty list, never null\").\n3. It guards a regression that has already occurred.\n4. It validates the interaction between two real components.\n\n**Do NOT add tests for:**\n\n- Trivial getters\u002Fsetters with no logic.\n- Behaviour already fully covered by an existing test.\n- Happy-path-only tests when edge cases exist and are untested.\n- Tests that always pass regardless of implementation.\n\n## Test Case Naming\n\nUse the format `TestUnit_Scenario_ExpectedOutcome`:\n\n```text\nTestParseConfig_MissingRequiredField_ReturnsError\nTestParseConfig_ValidInput_ReturnsParsedResult\n```\n\nSub-tests use plain, readable English:\n\n```text\n\"missing required field returns error\"\n\"valid input with 3 items succeeds\"\n```\n\n## Anatomy of a Good Test\n\n1. **Arrange** — set up inputs and dependencies clearly; avoid hidden shared state.\n2. **Act** — single call to the unit under test.\n3. **Assert** — check the outcome and produce a message that explains the failure.\n\nKeep each test focused on **one behaviour**. When multiple scenarios exist, use\ntable rows rather than separate functions.\n\n## Corner Cases Checklist\n\nBefore marking a feature tested, ask:\n\n- What happens with a nil\u002Fnull\u002Fzero\u002Fempty input?\n- What happens at the boundary (first item, last item, exactly at a limit)?\n- What happens when a dependency fails halfway through?\n- What happens when the same operation runs concurrently?\n- What happens with the largest valid input?\n- What happens when required configuration is missing?\n",{"name":5,"description":7},"main","7f49640beb4e54c03150274a3c6ebc9a8c69acee",".github\u002Fskills\u002Ftesting-strategy","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad","https:\u002F\u002Fgithub.com\u002Faydabd","Software and test developer","2026-11-08 15:20:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add aydabd\u002Fcacad --skill testing-strategy",{"tool":37,"command":38},"bunx","bunx skills add aydabd\u002Fcacad --skill testing-strategy",{"tool":40,"command":41},"pnpm","pnpm dlx skills add aydabd\u002Fcacad --skill testing-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftesting-strategy\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M78EEA900K1PTV7SDXV3HPTZ","token-optimization","Use zero-install context minimization first, with optional local optimization tooling when available.","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftoken-optimization\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M78EE5VW7RMH9T9HQ03CBBJ8","testing-patterns","Test implementation patterns. Use this when writing tests — table-driven tests, mocking, fixtures, assertions, and parallel execution.","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftesting-patterns\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78EE3H2ZS8A62AQX4V81VD8","testing-integration","Integration and E2E testing design. Use this when writing integration tests, E2E tests, or deciding what belongs in each test layer.","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftesting-integration\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78EE23Y2VDQHESDR0SGNT1R","test-review","Test review for missing coverage, weak assertions, flaky tests, isolation, fixtures, and regression risk.","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-review\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78EDZA2Q5WG9D7GD32QADKR","test-impact-selection","Select the minimal useful tests to run based on changed files, impacted components, and repository conventions.","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-impact-selection\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78EDXY2WMSPVHYJE8GDA4JK","severity-classification","Classify review findings into blocking, non-blocking, or note with consistent merge-risk rules.","https:\u002F\u002Fgithub.com\u002Faydabd\u002Fcacad\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fseverity-classification\u002FSKILL.md",[],[]]