Skip to main content

coverage-summary

Runs kueue-operator unit tests with coverage and produces a comprehensive Markdown report covering package and function coverage, E2E test inventory, gaps, findings, and recommendations. Use when asked for a coverage report, summary, or analysis.

Informations de source

Dépôt
openshift/kueue-operator
Dernière activité de la source
11 septembre 2026 à 19:43
Langue détectée de SKILL.md
anglais
Étoiles
9
Forks
29

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
coverage-summary
description
Runs kueue-operator unit tests with coverage and produces a comprehensive Markdown report covering package and function coverage, E2E test inventory, gaps, findings, and recommendations. Use when asked for a coverage report, summary, or analysis.
user-invocable
true
Run the unit tests with coverage and generate a comprehensive summary report. Execute the following steps: 1. Run unit tests with coverage: ```bash go test -mod=vendor -coverprofile=coverage.out -covermode=atomic ./pkg/... 2>&1 | tee /tmp/test_output.txt ``` 2. Get the overall coverage percentage: ```bash go tool cover -func=coverage.out | tail -1 ``` 3. Generate and display a comprehensive coverage summary that includes: **Overall Coverage** - Total statement coverage percentage **Unit Test Coverage** - List packages with tests and their coverage percentages - Categorize by coverage level (High ≥90%, Medium 80-89%, Low <80%) - List packages with 0% coverage - Distinguish between core packages and generated code **E2E Tests** - Count and list E2E test files - Show file sizes for major test files **Detailed File Coverage** - Show function-level coverage for tested packages **Test Commands** - Document available test commands (unit, e2e, disruptive, etc.) **Key Findings** - Strengths: What's well-tested - Critical Gaps: What needs tests - Recommendations: Priority improvements **Summary Statistics** - Total packages scanned - Percentage with tests - Percentage with 0% coverage - Generated code packages vs core logic packages Format the output as a clear, well-structured markdown report with tables, bullet points, and sections.
Voir sur GitHub