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

Fix flaky TaxonomyBrowser visualization unit tests

Abierto
#581 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@atiannicelli ya está trabajando en esto.

Desde el 15/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Type

Bug

Scope

Multi-theme or Platform

Skillset

dev ops

Description

Some TaxonomyBrowser visualization tests in src/components/__tests__/taxonomyBrowser.test.jsx fail intermittently. When they fail, Unit tests and are-we-good fail on PRs that don't touch the component. For example, #580 changes only an .mdx file and failed, then passed on re-run (failed job).

Failures seen:

  • viewport zoom and pan > still works when a zoom control is pressed with a shaky hand: expected 1 to be greater than 1
  • viewport zoom and pan > pans by the drag delta: expected { x: +0, y: +0, k: 1 } to match object { x: 60, y: 30 }
  • canvas sizing > fills the space it is given rather than a fixed size

Local repro on main code: npx vitest run src/components/__tests__/taxonomyBrowser.test.jsx failed 2/30 runs. Running only -t "viewport zoom and pan" passed 30/30, so earlier tests in the file seem to be involved.

Suspected cause (unconfirmed): showSunburst() returns once the sunburst is in the DOM, possibly before its passive effects run. Those effects are the window pointer listeners and the mount-time resetView() in src/components/taxonomyViz.jsx. A late resetView() would undo the test's zoom or pan.

Acceptance criteria:

  • Find and fix the root cause in the component or tests, without just adding retries.
  • The full test file passes on repeated local runs, e.g. 50 in a row.
Lenguaje dominante
MDX
Estrellas
84
Forks
30
Merge medio
13 h 13 min
PR fusionados (30 d)
33

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 OvertureMaps/docs

Todos los issues de OvertureMaps/docs

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.