“coverage”的搜索结果

Use the open-source free `ReportGenerator` tool for turning .NET coverage outputs into HTML, Markdown, Cobertura, badges, and merged reports. USE FOR: the repo uses or wants ReportGenerator; CI needs human-readable coverage reports; multiple coverage files must be merged. DO NOT USE FOR: raw coverage collection with no reporting need. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

中文简介正在准备中。当前显示原文说明。

Audit a test file or suite; produce a severity-ranked diagnostic report. ALWAYS USE for tests that verify nothing, missing/tautological assertions, swallowed/broad exceptions, flaky/order-dependent tests, duplication, or magic values. Polyglot. DO NOT USE for direct edits: writing-mstest-tests owns supplied MSTest assertions/attributes/lifecycle; code-testing owns new tests. Exclude running tests, migration, assertion metrics (assertion-quality), raw .NET coverage collection (run-tests), non-.NET coverage collection/analysis (native tooling), project-wide .NET coverage/CRAP (coverage-analysis), named-target .NET CRAP (crap-score), behavioral/pseudo-mutation gaps (test-gap-analysis), test-mix/ happy-vs-error classification and trait distributions (test-tagging), or the testsmells.org catalog (test-smell-detection).

中文简介正在准备中。当前显示原文说明。

Analyze test coverage gaps and generate tests to improve coverage. Use when improving test coverage, finding untested code, or writing missing tests.

中文简介正在准备中。当前显示原文说明。

Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing frameworks (pytest, Jest, JUnit, Go testing, etc.) and generates targeted test suggestions based on coverage analysis.

中文简介正在准备中。当前显示原文说明。

Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, realistic targets by company stage, and the action to take when each metric goes red. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate." Not for: building the dashboard UI (Allure/Grafana) — use qa-dashboard; measuring coverage gaps and mutation score — use coverage-analysis. Related: qa-dashboard, coverage-analysis, ci-cd-integration, release-readiness, quality-postmortem.

中文简介正在准备中。当前显示原文说明。

Generate Coverage and insurance resources with payer diversity including Medicare, Medicaid, commercial, Tricare, VA, and self-pay. Use when user mentions coverage, insurance, payer, Medicare, Medicaid, benefits, or coordination of benefits. For claims and EOB see the claims-eob skill.

中文简介正在准备中。当前显示原文说明。

解析 Verilator coverage.dat + sim log，输出 functional + code coverage 数值，判断是否 100% 达标。触发场景：(1) bb-invoke-verilator 后；(2) 每次回归后；(3) 显式 /bb-collect-coverage。

中文简介正在准备中。当前显示原文说明。

Calculates CRAP (Change Risk Anti-Patterns) score for .NET methods, classes, or files. Use when the user asks to assess test quality, identify risky untested code, compute CRAP scores, or evaluate whether complex methods have sufficient test coverage. Requires code coverage data (Cobertura XML) and cyclomatic complexity analysis. DO NOT USE FOR: writing tests, general test execution unrelated to coverage/CRAP analysis, or general code coverage reporting without CRAP context.

中文简介正在准备中。当前显示原文说明。

Analyze test coverage with detailed metrics, identify gaps, and generate comprehensive reports. Use when measuring code coverage, finding untested code, or validating coverage thresholds.

中文简介正在准备中。当前显示原文说明。

Validates detection coverage by mapping Atomic Red Team tests to ATT&CK techniques, checking which of your detections cover each tested technique, and reporting coverage gaps. Activates for requests to validate detections with atomic tests, map Atomic Red Team to coverage, or find detection gaps against tested techniques.

中文简介正在准备中。当前显示原文说明。

Maps hunts and detections to MITRE ATT&CK for coverage analysis: tagging hypotheses with techniques, building a coverage matrix from completed hunts, and identifying high-risk gaps to prioritize next. Activates for requests to map hunts to ATT&CK, build a coverage heatmap, or find detection gaps by technique.

中文简介正在准备中。当前显示原文说明。

Create QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what should we test", "prioritize testing", "risk-based testing", "test coverage plan", "QA approach for this project", "coverage matrix", "test scope", "how should we approach testing this quarter", "where are our coverage gaps", or any request to define the strategic plan for testing - not the execution of it. Also trigger at project kickoff when a QA lead asks "how do we approach quality on this?"

中文简介正在准备中。当前显示原文说明。

Comprehensive test suite review across five phases. Surveys unit coverage, integration coverage, E2E (browser) coverage for webapps, fuzz coverage, and test quality — in that order. Advisory only — produces findings and proposes tickets; does not implement test changes.

中文简介正在准备中。当前显示原文说明。

An innate exploratory drive that guarantees no graph node remains permanently invisible to an agent population. After a warm-up period (step > 3), each agent fires a coverage scan with probability |unseen_nodes| / |all_nodes|. When triggered, the agent teleports directly to the globally unseen node with the highest belief uncertainty, works it, and returns control to the normal action-selection loop. Probability is self-annealing: it starts near 1.0 when almost everything is unseen and decays toward 0.0 as coverage saturates, requiring no manual schedule. The mechanism is "innate" (hard-coded into the agent step loop) as distinct from the "adaptive" EFE path, which requires local neighbors and learned precision weights. Together they form a two-layer exploration architecture: adaptive for locally-guided foraging, innate for topological completeness.

中文简介正在准备中。当前显示原文说明。

Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.

中文简介正在准备中。当前显示原文说明。

Coverage review and verification sufficiency routing. Use when test coverage, uncovered paths, coverage reports, or verification adequacy need a read-only QA review; do not use for writing tests or running browser/E2E artifacts.

中文简介正在准备中。当前显示原文说明。

测量OpenClaw测试和插件验证的耗时与内存使用，调查模块加载及启动过程中的原因，在保留测试验证范围的同时改进，并比较变更前后的数值。

• 调查测试缓慢和模块加载开销
• 减少插件验证耗时和内存使用
• 调查测试期间的内存增长

为Kotlin代码先编写测试，使用Kotest和MockK验证行为与依赖交互，涵盖异步测试、生成输入的属性测试及Kover覆盖率检查。

• 为现有Kotlin代码补充测试
• 先写测试再开发新功能
• 验证协程和Flow的行为

从测试开始实现 Laravel 功能，使用 PHPUnit 或 Pest 验证模型、API、身份认证和权限，模拟外部服务，并通过覆盖率了解测试执行了哪些代码。

• 从测试开始实现 Laravel 功能
• 验证 API 身份认证与权限
• 模拟支付、邮件和队列

在合并或部署Laravel项目前，依次检查环境、代码、测试覆盖率、依赖漏洞、数据库变更、缓存、队列及定时任务；前置检查失败时停止后续操作。

• 创建Laravel拉取请求前检查
• 重大重构或依赖更新后验证
• 部署至预发布或生产环境前检查

按先写测试的流程开发Go代码，支持多组用例、HTTP响应验证、性能基准测试、自动生成输入的模糊测试，以及查看测试执行范围的覆盖率检查。

• 先写测试再开发Go代码
• 补充正常与异常测试用例
• 比较运行时间和内存分配量

在Django发布或提交变更提案前，依次检查环境、代码质量、数据库变更、测试、漏洞及配置，汇总各阶段是否通过和需要修复的问题。

• 提交Django变更提案前检查
• 检查数据库迁移
• 核对测试覆盖率目标

将项目质量标准及其数值、理由和检查方法写入文档，并从差异中检查跳过测试、抑制警告或降低门槛的改动，维持智能体开发质量。

• 制定智能体开发的质量标准
• 选择覆盖率与性能目标
• 发现跳过测试或抑制警告

检查重复、缺乏实质验证或依赖内部实现的测试，逐项确认删除依据与保留的替代测试，在保留问题复发检测能力的前提下，合并、修复或删除测试。

• 审查重复测试
• 保留回归检测能力并整理测试
• 重新评估依赖内部实现的测试