[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DF6WCME1Q0NPENJHS5CEHA":3,"skill-same:01M7DF6WCME1Q0NPENJHS5CEHA":51},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DF6WCME1Q0NPENJHS5CEHA","integration-testing",null,"Test a component with its real collaborators or local stand-ins through the repository's integration setup. Use when behavior across a component boundary cannot be proven with isolated unit tests.","andersonmrodrigues\u002Fpaved","andersonmrodrigues","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13907380?v=4","01M7DEV3FP2VMQZ3FP2FP1TK1C","Anderson Rodrigues","01M7DEV3GC2QAQBW4FMNT98H48",1,"MIT","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Ftesting\u002Fintegration-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: integration-testing\ndescription: >-\n  Test a component with its real collaborators or local stand-ins through the repository's integration setup. Use when behavior across a component boundary cannot be proven with isolated unit tests.\n---\n\n# Integration testing\n\n## When to use\n\nWhen a claim concerns a boundary: data written and read back, a message published and\nconsumed, a remote contract honored, configuration actually loaded, a transaction\ncommitted or rolled back.\n\n## Required context\n\nThe verification profile (how integration tests run, what they need). Useful: the\nintegrations context (which external systems exist and how the project stands them up\nfor tests) and the technology context.\n\n## Preconditions\n\n- The project has a way to run integration tests. If the profile marks `integration` as\n  unavailable, record a gap; do not build test infrastructure unasked.\n- The claim names the boundary under test.\n\n## Procedure\n\n1. **Discover the existing setup**: where integration tests live, how collaborators are\n   started (local instances, containers, in-memory stand-ins, recorded responses), how\n   data is seeded and cleaned up, and how tests are kept apart from unit tests.\n2. **Test through the real boundary.** Use real collaborators or the project's accepted\n   stand-ins; a double for the very boundary under test defeats the purpose.\n3. **Own the data.** Each test creates what it needs and does not depend on data from\n   another test or on execution order. Clean up the same way sibling tests do.\n4. **Cover the failure side of the boundary**: the collaborator is unavailable, slow,\n   returns an error or malformed data, or a constraint is violated.\n5. **Keep test configuration separate** from real configuration. Credentials for test\n   collaborators come from the environment or the test setup, never from real\n   environments and never written into files.\n6. **Run the tests twice**: an unstable result on the second run means shared state or\n   timing problems to fix now.\n\n## Tools\n\nNone. The command comes from the verification profile.\n\n## Rules\n\n`core.architecture.follow-existing-patterns`: reuse the existing setup rather than\nstarting collaborators a new way. `core.security.no-secrets-in-source` applies to test\nconfiguration and seeded data.\n\n## Verification\n\nRequired: `integration`.\n\n## Evidence\n\nA check result for the integration tests that cover the claim.\n\n## Completion criteria\n\n- Each boundary claim has a test that crosses the real boundary.\n- Tests pass on repeated runs and in any order.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Unit test in disguise | The boundary under test is replaced by a double | Use the real collaborator or its accepted stand-in |\n| Order dependence | Tests pass alone and fail together | Give each test its own data |\n| Environment leak | Tests reach a shared or real environment | Stop; point them at the test setup |\n| Slow suite | New tests add large startup cost | Reuse the existing shared setup |\n\n## References\n\nNone.\n","# Integration testing\n\n## When to use\n\nWhen a claim concerns a boundary: data written and read back, a message published and\nconsumed, a remote contract honored, configuration actually loaded, a transaction\ncommitted or rolled back.\n\n## Required context\n\nThe verification profile (how integration tests run, what they need). Useful: the\nintegrations context (which external systems exist and how the project stands them up\nfor tests) and the technology context.\n\n## Preconditions\n\n- The project has a way to run integration tests. If the profile marks `integration` as\n  unavailable, record a gap; do not build test infrastructure unasked.\n- The claim names the boundary under test.\n\n## Procedure\n\n1. **Discover the existing setup**: where integration tests live, how collaborators are\n   started (local instances, containers, in-memory stand-ins, recorded responses), how\n   data is seeded and cleaned up, and how tests are kept apart from unit tests.\n2. **Test through the real boundary.** Use real collaborators or the project's accepted\n   stand-ins; a double for the very boundary under test defeats the purpose.\n3. **Own the data.** Each test creates what it needs and does not depend on data from\n   another test or on execution order. Clean up the same way sibling tests do.\n4. **Cover the failure side of the boundary**: the collaborator is unavailable, slow,\n   returns an error or malformed data, or a constraint is violated.\n5. **Keep test configuration separate** from real configuration. Credentials for test\n   collaborators come from the environment or the test setup, never from real\n   environments and never written into files.\n6. **Run the tests twice**: an unstable result on the second run means shared state or\n   timing problems to fix now.\n\n## Tools\n\nNone. The command comes from the verification profile.\n\n## Rules\n\n`core.architecture.follow-existing-patterns`: reuse the existing setup rather than\nstarting collaborators a new way. `core.security.no-secrets-in-source` applies to test\nconfiguration and seeded data.\n\n## Verification\n\nRequired: `integration`.\n\n## Evidence\n\nA check result for the integration tests that cover the claim.\n\n## Completion criteria\n\n- Each boundary claim has a test that crosses the real boundary.\n- Tests pass on repeated runs and in any order.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Unit test in disguise | The boundary under test is replaced by a double | Use the real collaborator or its accepted stand-in |\n| Order dependence | Tests pass alone and fail together | Give each test its own data |\n| Environment leak | Tests reach a shared or real environment | Stop; point them at the test setup |\n| Slow suite | New tests add large startup cost | Reuse the existing shared setup |\n\n## References\n\nNone.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","plugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Ftesting\u002Fintegration-testing",0,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues","2026-11-14 20:09:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add andersonmrodrigues\u002Fpaved --skill integration-testing",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill integration-testing",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill integration-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Ftesting\u002Fintegration-testing\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"skill.yaml","REFERENCE","参考文档",369,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fpaved\u002Fruntime\u002Fpaved-core\u002Fcore\u002Fskills\u002Ftesting\u002Fintegration-testing\u002Fskill.yaml",[52,59,65,71,77,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DFBWJT4T1MPBHTWT19PBEK","sample-skill","Does a sample task. Use when a sample is needed.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":55,"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},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\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},"01M7DFBFAD0RYCRHTZ2JW4RX7E","no-activation","Does a sample task.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fno-activation\u002FSKILL.md",[],[]]