Move the integration test suite to Playwright

Abierto
  • ¿Algo no está bien?
#7,617 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, playwright, python
Área
ci-cd, testing, web-dev

Línea de trabajo

Start with tests/integration/ and tests/integration/tests_playwright/, then read CLAUDE.md for the preferred Playwright test layout. Review tests/integration/utils.py and the CI workflows to identify Selenium helpers, coverage modes, and matrix legs; related issue #6384 covers navigation waits. Done means the remaining integration coverage runs through Playwright with one gated workflow and no Selenium dependency.

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

Descripción

roadmap

Summary

Finish migrating tests/integration/ from Selenium to Playwright, so there is one browser-driving harness, one set of test utilities and one CI gate to maintain.

Current state

  • tests/integration/*.py holds 44 modules, 34 of them driving Selenium (run in dev and prod modes).
  • tests/integration/tests_playwright/ holds 27 modules and is the preferred home for new tests (see CLAUDE.md).
  • Both suites build apps through AppHarness, but keep separate polling and assertion helpers.

Plan

  1. Port each Selenium module into tests_playwright/, extending an existing Playwright app rather than creating a new one when the cases are small.
  2. Replace the Selenium-era helpers in tests/integration/utils.py (polling, event ordering, storage access) with Playwright-native waits and expect assertions; #6384 covers the navigation helper.
  3. Keep dev and prod coverage where the Selenium suite had it.
  4. Remove Selenium, its CI matrix legs and its dependency, and collapse the integration workflows into a single gated workflow.

Related

  • #6384 integration tests: switch poll_for_navigation to Playwright wait_for_url
  • #7611 unit tests for the shipped frontend JavaScript (the unit-level complement)
Lenguaje dominante
Python
Estrellas
29k
Forks
1.8k
Merge medio
2 d 22 h
PR fusionados (30 d)
143

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 reflex-dev/reflex

Todos los issues de reflex-dev/reflex

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.