Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add test coverage reporting with a minimum per package

Cerrado
#177 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, typescript

Línea de trabajo

Start with vitest.config.ts, the root package manifest, and the CI test step; check CONTRIBUTING.md for setup notes and build before testing. Add the matching coverage provider, configure src/** coverage and per-package line and branch thresholds, then run pnpm test:coverage on dev to measure and verify the package table. Done when CI uses that script and it passes with thresholds rounded down to the nearest 5.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement good first issue hacktoberfest testing

vitest.config.ts only lists the three test projects, and no coverage provider is installed, so we can't see which code has no tests.

What to do

  • Add @vitest/coverage-v8 (matching the installed vitest major) as a root dev dependency.
  • Configure coverage for packages/core, packages/server and packages/widget, covering src/** only, with the text and lcov reporters.
  • Run it once on dev and set per-package thresholds (lines and branches) at the current numbers rounded down to the nearest 5, so CI fails if coverage drops.
  • Add a test:coverage script and use it in the CI test step instead of pnpm test.

Acceptance criteria

  • pnpm test:coverage prints a table per package and passes on dev
  • The thresholds you picked are in the PR description with the measured numbers
  • coverage/ stays ignored (it already is in .gitignore)
  • No changeset needed (tooling only)

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #<this issue number>. Setup notes (pnpm, build before test) are in CONTRIBUTING.md.

Lenguaje dominante
TypeScript
Estrellas
13
Forks
7
Merge medio
4 h 11 min
PR fusionados (30 d)
122

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codercops/chatcops

Todos los issues de codercops/chatcops

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.