The Home e2e test can pass while the standing panel is missing
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 82/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- cli, testing-qa
Línea de trabajo
Start with the standing entry at internal/e2e/tuiwords_test.go:186 and the tagged Home assertion in internal/e2e/tui_e2e_test.go. Run TestTUIE2E and inspect the matcher against a captured or fake Home frame where standing appears outside the panel. Done means the bounded panel check rejects the false positive, includes a unit test, and records the strengthened oracle in invalidates.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Seen on dev@debffabf6. Surfaced while verifying #1415; not introduced by it.
What happened
The e2e needle for Home's standing panel is only standing. Other screen text can contain that word, so the test may pass even if the panel heading or its rows are absent. The cheap source-word gate checks that the literal exists, not that it occupies the correct screen block.
Replication
Deterministic (no model). Inspect the standing entry in the tuiWord table. In a captured Home frame containing standing elsewhere, remove the panel block and apply the current substring assertion; it still matches. A fake Home frame can drive this without a model.
Where
internal/e2e/tuiwords_test.go:186 at dev@debffabf6 supplies the bare word. The tagged Home assertion in internal/e2e/tui_e2e_test.go consumes that needle.
The fix
Assert the heading within the panel's own bounded block and at least one expected row or empty-panel whisper for the fixture.
Acceptance
- e2e:
TestTUIE2Efails if thestandingpanel is removed while another part of Home still saysstanding. - Unit: the panel-block matcher rejects that false-positive frame.
- Record the strengthened oracle in the test change entry's
invalidates.
- Lenguaje dominante
- Go
- Estrellas
- 115
- Forks
- 14
- Merge medio
- 9 h 38 min
- PR fusionados (30 d)
- 730
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Agent-Field/CodeAF
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Agent-Field/CodeAF#1489 ·
-
area:chat bug good first issue sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Agent-Field/CodeAF#1470 ·
-
area:chat bug good first issue sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Agent-Field/CodeAF#1469 ·
-
area:chat bug sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Agent-Field/CodeAF#1468 ·
-
area:tests bug hygiene sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Agent-Field/CodeAF#1460 ·
Todos los issues de Agent-Field/CodeAF
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
prometheus/procfs#872 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
bazel-contrib/rules_go#4726 · 1 comentario ·
-
area/auto-scaling area/monitoring area/ops-productivity kind/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100