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

Make e2e tests mandatory for PR merging

Abierto
#4,284 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 3 días

@clairep94 ya está trabajando en esto.

Desde el 1/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Enhancement On Hold
Increasing Access

Unsure

Feature enhancement details

Context:

This issue is a followup from GSOC:

  • @Geethegreat has create an e2e test suite for his GSOC 2026 project
  • We purposely made it so that e2e tests were not required for merging PR's so that the GSOC project did not unnecessarily block other work on the repo
  • We also purposely made it so that e2e tests were gated by approval from @Geethegreat, @clairep94, @khanniie, or @raclim during the GSOC period, so that we did not accidentally overspend on GHA hours

  • Now that GSOC is complete, we should update so that the e2e test suite is mandatory for merging into develop
  • Ideally we should update to:
    • Remove the approval gating
    • Have e2e tests trigger automatically after successful unit tests
    • Add some concurrency rules to ensure this doesn't result in a lot of GHA hours useage
      • Cancel any in-progress runs if a later run is triggered
      • Maybe debounce triggers if this is possible
    • Ideally update to minimize the required amount of time for e2e tests to run:
      • Make app startup in CI faster if possible
      • Caching any installations (some work previously done here already)

--> Will self-assign this issue

Requirements:

  • Access to repo settings > environments & branch protection
Lenguaje dominante
JavaScript
Estrellas
1.7k
Forks
1.7k
Merge medio
5 d 15 h
PR fusionados (30 d)
9

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 processing/p5.js-web-editor

Todos los issues de processing/p5.js-web-editor

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.