[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARTYTKBPTHC3EDNZ0JTTYB":3,"skill-same:01M7ARTYTKBPTHC3EDNZ0JTTYB":46},{"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":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ARTYTKBPTHC3EDNZ0JTTYB","test-coverage-map",null,"Maps what is tested and what is not by requirement, journey, code area and test level, not only line coverage, and shows the pyramid shape. Use when the user says 'coverage gaps' or asks 'what is not tested' or 'which requirements have no tests'. Not for the quality of each test (use testcase-reviewer).","quark-sri\u002Fqestack","quark-sri","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89900424?v=4","01M7ARN6E370E8C9T165BKJB5G","Srinivas Pasupulati","01M7ARN6F6BCMFYCV5RC5HR9JC",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftest-coverage-map\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-coverage-map\ndescription: \"Maps what is tested and what is not by requirement, journey, code area and test level, not only line coverage, and shows the pyramid shape. Use when the user says 'coverage gaps' or asks 'what is not tested' or 'which requirements have no tests'. Not for the quality of each test (use testcase-reviewer).\"\nlicense: Apache-2.0\nargument-hint: \"[repository, module, feature or requirement set]\"\n---\n\n# test-coverage-map\n\n## Objective\n\nLine coverage shows which lines ran. It does not show which rules are checked, or which requirements have no test. This skill maps the tests to requirements and to code areas, rates each target as covered, weak or untested, and ranks the gaps by risk.\n\n## Context\n\n1. Read `.agents\u002Fqa-project-context.md` if it exists. Use its test levels, requirement sources and coverage reports.\n2. If it does not exist, find the tests, the requirement sources and any coverage report in the repository. Suggest `qa-project-context` once. Do not stop the work for it.\n\n## Discovery questions\n\n1. What is the scope: the whole repository, a module, a feature, a set of requirements?\n2. Where are the requirements (specs, stories, contracts, documentation)?\n3. Does a coverage report exist, or may the coverage command run?\n\n## Workflow\n\n1. **Inventory the tests.** For each test file, note the level: unit, component or API, integration, contract, or end-to-end UI. Note the area that it tests, and the requirement IDs or behaviors that it names.\n2. **Inventory the targets:** requirements and acceptance criteria, code areas (modules, services, public functions, endpoints), and user journeys.\n3. **Map** each test to the targets. Use explicit links first (IDs in names, tags, comments), then the code that the test calls. Mark each link as explicit or inferred.\n4. **Rate each target:** COVERED (at least one strong test that checks values or effects), WEAK (only weak tests, or only end-to-end tests for a business rule), UNTESTED.\n5. **Line coverage.** Read an existing report, or run the coverage command with the user's agreement. Mark risky code without coverage: error paths, validation, calculations, permission checks.\n6. **Test pyramid.** Count the tests at each level, and name the shape problems.\n7. **Rank the gaps** by risk (see `risk-based-testing`).\n\n## Output\n\n```\n## Test coverage map: \u003Cscope>\n\n| Level | Tests | Share |\n|---|---|---|\n\n| Requirement \u002F behavior | Status | Tests (explicit \u002F inferred) | Note |\n|---|---|---|---|\n\n| Code area | Status | Line coverage | Risky untested paths |\n|---|---|---|---|\n\nTop gaps to close: \u003Ctarget> - why - the test to add, and its level\n```\n\n## Anti-patterns\n\n- **Line coverage as the answer.** A covered line with no assertion is not tested.\n- **Inferred links shown as facts.** Mark them.\n- **Equal weight for all gaps.** An untested permission check matters more than an untested log line.\n\n## Done when\n\n- Each requirement and code area in scope has a status, with explicit or inferred links.\n- The test pyramid shape is described.\n- The top gaps are ranked by risk, each with the test to add.\n\n## Related skills\n\n- `risk-based-testing`: the risk of each gap.\n- `testcase-reviewer`: the quality of the tests that exist.\n- `mutation-probe`: whether covered code is really checked.\n- `test-strategy`: the target shape of the suite.\n","# test-coverage-map\n\n## Objective\n\nLine coverage shows which lines ran. It does not show which rules are checked, or which requirements have no test. This skill maps the tests to requirements and to code areas, rates each target as covered, weak or untested, and ranks the gaps by risk.\n\n## Context\n\n1. Read `.agents\u002Fqa-project-context.md` if it exists. Use its test levels, requirement sources and coverage reports.\n2. If it does not exist, find the tests, the requirement sources and any coverage report in the repository. Suggest `qa-project-context` once. Do not stop the work for it.\n\n## Discovery questions\n\n1. What is the scope: the whole repository, a module, a feature, a set of requirements?\n2. Where are the requirements (specs, stories, contracts, documentation)?\n3. Does a coverage report exist, or may the coverage command run?\n\n## Workflow\n\n1. **Inventory the tests.** For each test file, note the level: unit, component or API, integration, contract, or end-to-end UI. Note the area that it tests, and the requirement IDs or behaviors that it names.\n2. **Inventory the targets:** requirements and acceptance criteria, code areas (modules, services, public functions, endpoints), and user journeys.\n3. **Map** each test to the targets. Use explicit links first (IDs in names, tags, comments), then the code that the test calls. Mark each link as explicit or inferred.\n4. **Rate each target:** COVERED (at least one strong test that checks values or effects), WEAK (only weak tests, or only end-to-end tests for a business rule), UNTESTED.\n5. **Line coverage.** Read an existing report, or run the coverage command with the user's agreement. Mark risky code without coverage: error paths, validation, calculations, permission checks.\n6. **Test pyramid.** Count the tests at each level, and name the shape problems.\n7. **Rank the gaps** by risk (see `risk-based-testing`).\n\n## Output\n\n```\n## Test coverage map: \u003Cscope>\n\n| Level | Tests | Share |\n|---|---|---|\n\n| Requirement \u002F behavior | Status | Tests (explicit \u002F inferred) | Note |\n|---|---|---|---|\n\n| Code area | Status | Line coverage | Risky untested paths |\n|---|---|---|---|\n\nTop gaps to close: \u003Ctarget> - why - the test to add, and its level\n```\n\n## Anti-patterns\n\n- **Line coverage as the answer.** A covered line with no assertion is not tested.\n- **Inferred links shown as facts.** Mark them.\n- **Equal weight for all gaps.** An untested permission check matters more than an untested log line.\n\n## Done when\n\n- Each requirement and code area in scope has a status, with explicit or inferred links.\n- The test pyramid shape is described.\n- The top gaps are ranked by risk, each with the test to add.\n\n## Related skills\n\n- `risk-based-testing`: the risk of each gap.\n- `testcase-reviewer`: the quality of the tests that exist.\n- `mutation-probe`: whether covered code is really checked.\n- `test-strategy`: the target shape of the suite.\n",{"name":5,"license":15,"description":7,"argument-hint":24},"[repository, module, feature or requirement set]","main","33cd1b197739d1c9a7a907bc4bb50c00039c2371","plugins\u002Fqestack\u002Fskills\u002Ftest-coverage-map",0,"https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack","https:\u002F\u002Fgithub.com\u002Fquark-sri","2026-11-14 20:45:02",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add quark-sri\u002Fqestack --skill test-coverage-map",{"tool":38,"command":39},"bunx","bunx skills add quark-sri\u002Fqestack --skill test-coverage-map",{"tool":41,"command":42},"pnpm","pnpm dlx skills add quark-sri\u002Fqestack --skill test-coverage-map","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftest-coverage-map\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ARWD0Z563VXR17R8QMHWKE","unit-testing","Writes, fixes or improves unit tests for rules, calculations, validation and state logic: arrange-act-assert, exact oracles, boundary sets, doubles only at boundaries, controlled clock and randomness. Use when the user says 'write unit tests', 'TDD this' or 'mock this dependency'. Not for HTTP endpoints (use api-testing).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7ARW7HQKKAWQZ4K8128SBXC","ui-automation","Writes, fixes or structures browser end-to-end tests for critical journeys: role, label or test ID locators, auto-waiting assertions, API data setup, page objects, auth reuse and traces. Use when the user says 'UI test', 'end-to-end test' or 'our UI tests are brittle'. Not for business rules (use unit-testing).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Fui-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7ARW22645WR7R6MKTAP1CVP","testcase-reviewer","Reviews automated tests or manual test cases like a senior test architect: scores fidelity, oracles, assertion depth, edge cases and determinism, and finds tests that pass on wrong code. Use when the user says 'review my tests', 'test smells' or 'review AI-written tests'. Not for fault injection (use mutation-probe).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftestcase-reviewer\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7ARVXYW0WTC5E7J5CR4S0EC","testability-review","Scores how testable a feature, module or design is before tests exist (seams for clock, randomness and network, hidden state, observability) and gives the smallest production change per blocker. Use when the user asks 'is this testable' or 'why is this hard to test'. Not for writing the tests (use unit-testing).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftestability-review\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ARVTENW2RDMMKHDTGMYQBM","test-strategy","Writes a test strategy for a product, system or team: quality goals, test levels and their share, environments, data, automation scope, non-functional testing, metrics and a roadmap. Use when the user says 'test strategy' or 'QA strategy'. Not for one sprint or release plan (use test-planning).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftest-strategy\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ARVMXVKN1XHB1QQCRNGXP5","test-runner","Finds how a project runs its tests, runs the right subset, and triages each failure as product bug, test defect, environment problem or flaky test, with evidence. Use when the user says 'run the tests' or asks 'which tests fail and why'. Not for pipeline design (use ci-cd-integration).","https:\u002F\u002Fgithub.com\u002Fquark-sri\u002Fqestack\u002Fblob\u002Fmain\u002Fplugins\u002Fqestack\u002Fskills\u002Ftest-runner\u002FSKILL.md",[],[]]