[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSFEXV48X8YQSRPFZHVN50":3,"skill-same:01M7CSFEXV48X8YQSRPFZHVN50":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSFEXV48X8YQSRPFZHVN50","test-doubles-wiremock",null,"Use when a test would otherwise call a real external dependency - replace it with WireMock or an equivalent stub so runs are deterministic, offline, and control the responses","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Ftest-doubles-wiremock\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-doubles-wiremock\ncategory: testing\ndescription: Use when a test would otherwise call a real external dependency - replace it with WireMock or an equivalent stub so runs are deterministic, offline, and control the responses\nenabled: false\n---\n# Test Doubles & WireMock\n\n## Overview\n\nAn automated test that calls a real third-party service (payment gateway, auth provider, partner API) is slow, flaky, costs money, and cannot exercise failure modes on demand. Replace those dependencies with a controllable stub — WireMock for HTTP — so the test owns every response.\n\n**Core principle:** The system under test is real; its external dependencies are stubbed. You test YOUR code's behavior against controlled inputs, not the third party's uptime.\n\n## When to Use \u002F When NOT\n\n- **Stub:** third-party\u002Fexternal HTTP services, payment\u002Femail\u002FSMS providers, partner APIs, anything you don't own or that has side effects\u002Fcost.\n- **Do NOT stub:** the product's own API or the code under test — driving those for real is the whole point. And do not stub the database; use a real test database instead (see test-database-seeding) so SQL\u002Fdialect behavior is genuine.\n\n## WireMock Essentials\n\nRun WireMock as a standalone server or a Testcontainers container; point the app's config for that dependency at its URL.\n\n```json\n\u002F\u002F stub: the auth provider returns a valid token for a known client\n{\n  \"request\":  { \"method\": \"POST\", \"url\": \"\u002Foauth\u002Ftoken\" },\n  \"response\": { \"status\": 200, \"jsonBody\": { \"access_token\": \"test-token\", \"expires_in\": 3600 } }\n}\n```\n\nModel the failure paths too — that's the value a real service won't give you on demand:\n\n| Scenario to cover | WireMock stub |\n|-------------------|---------------|\n| Happy response | 200 + expected body |\n| Upstream 5xx | `\"status\": 503` → assert your retry\u002Ffallback |\n| Timeout | `\"fixedDelayMilliseconds\": 30000` → assert your timeout handling |\n| Malformed body | 200 + garbage → assert you don't crash |\n| Auth rejected | 401 → assert your error surfaces cleanly |\n\n## Rules\n\n- **Verify the request too**, not just the canned response: assert the app called the dependency with the right method\u002Fpath\u002Fbody (WireMock `verify`). A stub that always returns 200 hides a broken request.\n- **Reset stubs between tests** so one test's mappings don't leak into another.\n- **Match the contract exactly** — stub the real endpoint's shape. A stub that diverges from reality passes tests but ships integration bugs; keep it aligned with the provider's documented contract.\n- Prefer per-test stubs over one giant global mapping file — tests stay readable and independent.\n\n## Worked Example\n\nCheckout calls an external payment API. To test \"payment declined shows an error and does not create an order\":\n1. WireMock stub: `POST \u002Fcharge` → `402 {\"error\":\"declined\"}`.\n2. Drive the real checkout flow against it.\n3. Assert: user sees the decline message, no order row was created, and WireMock recorded exactly one `POST \u002Fcharge` with the expected amount.\n\nNo real card, no real gateway, and the decline path is tested every run.\n\n## Common Mistakes\n\n- Stubbing your own API (you're no longer testing it).\n- Stubbing the database (use a real test DB).\n- A stub that returns 200 for everything → false green.\n- Never asserting the outgoing request → a broken payload passes.\n- Global stubs leaking across tests.\n\n## Red Flags\n\n- A test hits a real external URL → network flake and cost incoming.\n- Only the happy response is stubbed; no failure-mode coverage.\n- The stub shape drifted from the provider's real contract.\n","# Test Doubles & WireMock\n\n## Overview\n\nAn automated test that calls a real third-party service (payment gateway, auth provider, partner API) is slow, flaky, costs money, and cannot exercise failure modes on demand. Replace those dependencies with a controllable stub — WireMock for HTTP — so the test owns every response.\n\n**Core principle:** The system under test is real; its external dependencies are stubbed. You test YOUR code's behavior against controlled inputs, not the third party's uptime.\n\n## When to Use \u002F When NOT\n\n- **Stub:** third-party\u002Fexternal HTTP services, payment\u002Femail\u002FSMS providers, partner APIs, anything you don't own or that has side effects\u002Fcost.\n- **Do NOT stub:** the product's own API or the code under test — driving those for real is the whole point. And do not stub the database; use a real test database instead (see test-database-seeding) so SQL\u002Fdialect behavior is genuine.\n\n## WireMock Essentials\n\nRun WireMock as a standalone server or a Testcontainers container; point the app's config for that dependency at its URL.\n\n```json\n\u002F\u002F stub: the auth provider returns a valid token for a known client\n{\n  \"request\":  { \"method\": \"POST\", \"url\": \"\u002Foauth\u002Ftoken\" },\n  \"response\": { \"status\": 200, \"jsonBody\": { \"access_token\": \"test-token\", \"expires_in\": 3600 } }\n}\n```\n\nModel the failure paths too — that's the value a real service won't give you on demand:\n\n| Scenario to cover | WireMock stub |\n|-------------------|---------------|\n| Happy response | 200 + expected body |\n| Upstream 5xx | `\"status\": 503` → assert your retry\u002Ffallback |\n| Timeout | `\"fixedDelayMilliseconds\": 30000` → assert your timeout handling |\n| Malformed body | 200 + garbage → assert you don't crash |\n| Auth rejected | 401 → assert your error surfaces cleanly |\n\n## Rules\n\n- **Verify the request too**, not just the canned response: assert the app called the dependency with the right method\u002Fpath\u002Fbody (WireMock `verify`). A stub that always returns 200 hides a broken request.\n- **Reset stubs between tests** so one test's mappings don't leak into another.\n- **Match the contract exactly** — stub the real endpoint's shape. A stub that diverges from reality passes tests but ships integration bugs; keep it aligned with the provider's documented contract.\n- Prefer per-test stubs over one giant global mapping file — tests stay readable and independent.\n\n## Worked Example\n\nCheckout calls an external payment API. To test \"payment declined shows an error and does not create an order\":\n1. WireMock stub: `POST \u002Fcharge` → `402 {\"error\":\"declined\"}`.\n2. Drive the real checkout flow against it.\n3. Assert: user sees the decline message, no order row was created, and WireMock recorded exactly one `POST \u002Fcharge` with the expected amount.\n\nNo real card, no real gateway, and the decline path is tested every run.\n\n## Common Mistakes\n\n- Stubbing your own API (you're no longer testing it).\n- Stubbing the database (use a real test DB).\n- A stub that returns 200 for everything → false green.\n- Never asserting the outgoing request → a broken payload passes.\n- Global stubs leaking across tests.\n\n## Red Flags\n\n- A test hits a real external URL → network flake and cost incoming.\n- Only the happy response is stubbed; no failure-mode coverage.\n- The stub shape drifted from the provider's real contract.\n",{"name":5,"enabled":20,"category":24,"description":7},"testing","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Ftest-doubles-wiremock",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill test-doubles-wiremock",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill test-doubles-wiremock",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill test-doubles-wiremock","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Ftest-doubles-wiremock\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]