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

[quality] owners.ts: 13 behavioural mutants survive the suite, incl. a shared group cache key that gives every team the first team's members

Abierto
  • ¿Algo no está bien?
#574 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@hivecommons-hive ya está trabajando en esto.

Desde el 24/10/2026.

  • #575 de @hivecommons-hive — abierto

Evaluación

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

Línea de trabajo

The issue names the exact mutants by line in src/utils/owners.ts and prescribes the deliverable: a new __tests__/utils/ownersGuards.test.ts exercising expandGroups, parseOwners, loadOwnersTree, repoHasOwners and branchHasOwners with no src/ changes. Start by reading #572's harness notes, then reproduce with npx stryker run --mutate src/utils/owners.ts. Done is when the 13 listed mutants are killed (15 → 2 survivors, ~98.5%). Note: an open PR #575 already targets this issue, so it is effectively claimed.

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

Descripción

agent/quality needs-kind stage/040-covered-by-pr testing

Finding

Running the bounded Stryker harness proposed in #572 against src/utils/owners.ts (npx stryker run --mutate src/utils/owners.ts --force, Stryker 10.0.0, Vitest 5.0.4, main @ e3119ad) gives 332 mutants: 304 killed, 13 timed out, 15 survived (95.48%). Unit coverage of the file is 100/100/100/100 (npm run test:coverage @ e3119ad), so these are assertion gaps, not coverage gaps; the bundle suite runs the committed dist/index.js and cannot see a mutation of src/.

Thirteen of the survivors are behavioural (each applied by hand at its reported span and re-run to confirm):

Site Mutant What goes unpinned
owners.ts:151 memoized(groupCache, \${owner}/${slug}`, …)` key → '' Every team shares one cache entry: the second @org/team in an OWNERS set resolves to the first team's members. No test expands two distinct teams in one run.
owners.ts:99 parseGroup regex leading ^ removed alice@org/team is read as a group of org and a team is fetched for it
owners.ts:52 options !== null → true a bare options: key (YAML null) throws TypeError instead of meaning "no options"
owners.ts:278 file.content === undefined → false a blob with an encoding but no content fails with a Buffer TypeError, not "invalid OWNERS file returned from GitHub API for …" (only encoding-less blobs are tested)
owners.ts:468 repository?.default_branch ?. → . a payload with no repository at all throws instead of asking repos.get (every test payload carries a repository object)
owners.ts:482 isNotFound (6 mutants) guards → true / &&→|| a string or null rejection from git.getTree is never exercised; several arms would throw TypeError: Cannot use 'in' operator instead of the listing error
owners.ts:447 entry.path !== undefined → true a tree entry without a path throws inside probeBranchOwners (the same guard in loadOwnersTree is pinned)
owners.ts:398 hasOwnersCache key ${owner}/${repo} → '' repoHasOwners answers a second repository from the first
owners.ts:139 other-organization warning text → '' the only user-facing hint that a group was ignored

Not counted: owners.ts:161 (warning text, asserted exactly by held #564) and owners.ts:317 (core.debug text, equivalent by the review standard #572 documents).

Recommendation

Pin each contract in one new unit file, __tests__/utils/ownersGuards.test.ts, with direct expandGroups/parseOwners/loadOwnersTree/repoHasOwners/branchHasOwners calls (no src/ change). Re-running the harness with that file: 15 → 2 survivors (98.49%), both the exclusions above.

  • __tests__/utils/ownersGuards.test.ts pins the 13 behavioural mutants listed above

Priority

  • Impact: medium (the group-cache key is a real bug class for repositories that list two teams; the rest are guard contracts)
  • Effort: low

Refs #554 ("Strengthen assertions and the test harness" — a consumer of the mutation harness, not a tracker box of its own).

Filed by quality agent (hold-gated mode)

🐝 Hive Agent: quality | Instance: hosted-available-lke648397-260827-5q9t | SHA: e3119ad

— hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88

Lenguaje dominante
TypeScript
Estrellas
132
Forks
24
Merge medio
1 d 16 h
PR fusionados (30 d)
214

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 cncf/prow-github-actions

Todos los issues de cncf/prow-github-actions

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.