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

Fuzz every problem and language driver against the reference solutions

Abierto
  • ¿Algo no está bien?
#24 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, node.js
Área
backend, ci-cd, testing

Línea de trabajo

Start by reading backend/arena/runner/harness.js and the existing npm run validate:problems workflow to understand how reference solutions, problem metadata, and language drivers are run. Then inspect problem.function parameter types and the constraints referenced in issues #3 and #12. Done means the new seeded fuzzer supports the requested flags, shrinking, driver checks and CI run, and the stated validation commands pass.

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

Descripción

enhancement help wanted

Every problem is validated by running its JavaScript and Python references against its hand-written tests (npm run validate:problems). That only proves the references agree on inputs someone thought of. Bugs hide at the edges: empty arrays, negative numbers, duplicate values, maximum sizes, unicode strings.

What to do

Add backend/arena/scripts/fuzz-problems.js:

  • Generate random inputs from each problem's parameter types in problem.function (all types listed in #3), respecting declared constraints where present (see #12).
  • Bias generation toward edge cases: empty, single element, all equal, sorted, reverse sorted, min and max values.
  • Run both reference solutions on each input and compare with the problem's compare mode.
  • On a mismatch, shrink the input to the smallest failing case and print it, ready to paste into the problem as a new test.
  • Run every language driver in backend/arena/runner/harness.js on a reference solution too, so driver bugs in serialization (big integers, floats, nested tuples, unicode) are caught. New language drivers (#1, #2, #3, #5, #6) should pass this before merging.
  • Deterministic by seed. --seed, --runs and --problem flags.

Definition of done

  • Runs over all 45 problems locally in a few minutes with CODEARENA_RUNNER=local.
  • Prove it works: break one reference on purpose and show the fuzzer finding and shrinking the failure in the pull request.
  • Any real disagreements found get their own issues or fixes, with the shrunk input added as a test.
  • A short fuzz run (fixed seed, small run count) added to CI.
  • npm test and node scripts/check-boundary.js pass.
Lenguaje dominante
JavaScript
Estrellas
0
Forks
2
Sin PR fusionados en 30 d

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 sennaicodes/codearena

Todos los issues de sennaicodes/codearena

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.