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.

Informações da origem

Repositório
openshift/kueue-operator
Última atividade na origem
11 de setembro de 2026 às 19:43
Idioma detectado do SKILL.md
inglês
Estrelas
9
Forks
29

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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.
Ver no GitHub