Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Enforce frontend mutation testing as a required pull-request check

Aperta
  • Qualcosa non va?
#8,907 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, javascript
Ambito
ci-cd, frontend, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
PHP
Stelle
830
Fork
161
Merge medio
13h 34m
PR unite (30g)
493

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.