coverage-analysis
coverage-analysis
Catalogue généré le 2026-05-11
En une phrase
Coverage analysis measures code exercised during fuzzing.
Quand l'utiliser
- Use when assessing harness effectiveness or identifying fuzzing blockers.
Comment l'invoquer
- Slash command :
/coverage-analysis(si exposé dans ton CLI) - Phrases déclencheurs : voir la description complète ci-dessous
- Auto-invocation : sur demande explicite
Description complète
Coverage analysis measures code exercised during fuzzing. Use when assessing harness effectiveness or identifying fuzzing blockers.
Pour aller plus loin
Coverage Analysis
Coverage analysis is essential for understanding which parts of your code are exercised during fuzzing. It helps identify fuzzing blockers like magic value checks and tracks the effectiveness of harness improvements over time.
Overview
Code coverage during fuzzing serves two critical purposes:
- Assessing harness effectiveness: Understand which parts of your application are actually executed by your fuzzing harnesses
- Tracking fuzzing progress: Monitor how coverage changes when updating harnesses, fuzzers, or the system under test (SUT)
Coverage is a proxy for fuzzer capability and performance. While coverage is not ideal for measuring fuzzer performance in absolute terms, it reliably indicates whether your harness works effectively in a given setup.
Key Concepts
| Concept | Description |
|---|
(extrait — voir le SKILL.md complet pour la suite)
Source
- Plugin :
trailofbits/testing-handbook-skills - Nom interne :
coverage-analysis - Fichier :
/home/thymon/.claude/plugins/cache/trailofbits/testing-handbook-skills/1.0.1/skills/coverage-analysis/SKILL.md