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

Enforce frontend mutation testing as a required pull-request check

Abierto
  • ¿Algo no está bien?
#8,907 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, javascript
Área
ci-cd, frontend, testing

Línea de trabajo

Start with the validated StrykerJS pull-request workflow and the frontend mutation-testing merge policy documented from measured LibreSign data. Verify the applicable branch or ruleset configuration and whether GitHub merge queue requires the merge_group event. Validate the listed representative pull-request cases, and finish when the required check is current, blocks policy failures and operational errors, and reports success for no-op changes.

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

Descripción

frontend javascript

Goal

Enable the validated StrykerJS pull-request workflow as a required merge-protection check for LibreSign frontend changes.

This issue implements the policy decided by the parent epic. It does not redefine mutation thresholds or execution scope.

Prerequisites

The change-aware pull-request workflow must be stable and the frontend mutation-testing merge policy must be documented from measured LibreSign data.

Required behavior

  • Pull requests with mutation-relevant frontend changes receive the required mutation check before merge.
  • Pull requests without mutation-relevant changes still receive a successful status from the same check.
  • The check corresponds to the latest pull-request commit.
  • Operational Stryker/Vitest failures cannot result in a successful required status.
  • Mutation failures defined by the agreed policy block merge.
  • The configuration remains compatible with the repository's actual merge mechanism and branch/ruleset configuration.

If LibreSign uses GitHub merge queue, verify whether the workflow also needs the merge_group event before enabling the required check.

Validation

Before making the check required, validate representative cases:

  • source change with passing mutation result;
  • source change with an intentional surviving mutant;
  • test-only change that weakens mutation protection;
  • mutation timeout/error;
  • operational Stryker or Vitest failure;
  • no mutation-relevant change;
  • mutation/test infrastructure change requiring broader execution.

Done when

  • The frontend mutation check is required by the applicable LibreSign branch/ruleset policy.
  • A mutation regression defined by policy cannot be merged.
  • Operational failures cannot be merged as false green.
  • No-op PRs do not remain pending because the workflow skipped entirely.
  • The required check reflects the latest pull-request commit.
  • Merge-queue compatibility is verified when applicable.

Related

  • Parent epic: #8810
Lenguaje dominante
PHP
Estrellas
835
Forks
167
Merge medio
21 h 30 min
PR fusionados (30 d)
375

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 LibreSign/libresign

Todos los issues de LibreSign/libresign

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.