Remaining wall-clock dependent tests
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 56/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- playwright, typescript
- Área
- testing
Línea de trabajo
Start with the listed tests in test/surfaces/vite-plugin.test.ts and read how they handle the production debounce; identify how the current test setup can drive time deterministically. Then review the waits in test/scripts/demo-integration-signals.test.ts and test/surfaces/overlay-client.test.ts for assertions that can use positive signals. Done means the listed load-sensitive waits are addressed while the gated integration assertions remain unchanged.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What
Three load-sensitive tests were made deterministic before the freeze. A sweep found others that depend on real elapsed time and were left in place:
test/surfaces/vite-plugin.test.tsaround lines 837 to 853: three 20 ms pauses race a real 80 ms production debounce; a delayed sleep fires the debounce early and breaks the nothing-has-run assertions. The strongest remaining risk.test/surfaces/vite-plugin.test.tslines 561, 633, 781: 120 ms timers waiting out the same debounce with a 40 ms margin.test/scripts/demo-integration-signals.test.tslines 71 to 73: asserts under 1,000 ms around a real 50 ms bound.test/surfaces/scrub.test.tslines 468 to 474: under 8,000 ms over synchronous work.test/deps/real.integration.test.tslines 218 to 220 andtest/deps/readiness.real.test.ts: gated behind the integration flag; the latter are load-safe by direction.test/surfaces/overlay-client.test.ts: two waits that assert nothing happened (load only strengthens them), two 900 ms route delays staging stale-response races, and manyexpect.pollcalls at the 1,000 ms default around real Chromium round trips.
Direction
Drive the debounce with a fake clock in the vite plugin tests. Convert the nothing-happened waits to a positive signal. Leave the gated integration assertions.
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 2 h 48 min
- PR fusionados (30 d)
- 8
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
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 usabl-dev/usabl
-
area: engine bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictAbiertoarea: assistants bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
area: engine bug security
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedAbiertoarea: overlay bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
-
area: engine enhancement performance
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de usabl-dev/usabl
Issues similares
-
[Bug]: Circular app layout navigation and help icons are shifted upward in the official demoAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
cloudscape-design/components#5184 ·
Los mantenedores suelen responder en 2 días
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
JarX-Concepts/react-native-platform-components#130 ·
Los mantenedores suelen responder en 1 día
-
fix(api): optimize-for-web /preview outer catches miss asDecoderOutOfMemory on V8 OOM and SIGKILLAbiertoarea: backend bug priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
snapotter-hq/SnapOtter#3773 ·
Los mantenedores suelen responder en 1 día
-
ai-driven-qa ux-audit
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
linagora/twake-contacts-frontend#386 ·
Los mantenedores suelen responder en 1 día
-
git: README should state plainly that without --repository every reachable repository is in scopeAbiertodocumentation server-git v2
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
modelcontextprotocol/servers#5225 ·
Los mantenedores suelen responder en 1 día