Move the integration test suite to Playwright

Aperta
  • Qualcosa non va?
#7,617 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, playwright, python
Ambito
ci-cd, testing, web-dev

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)
Lingua principale
Python
Stelle
29k
Fork
1.8k
Merge medio
2g 22h
PR unite (30g)
143

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di reflex-dev/reflex

Tutte le issue di reflex-dev/reflex

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.