Move the integration test suite to Playwright

Ouverte
#7,617 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active
Stack technique
github-actions, playwright, python
Domaine
ci-cd, testing, web-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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)
Langage dominant
Python
Étoiles
29k
Forks
1.8k
Merge moyen
2 j 22 h
PR mergées (30 j)
143

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de reflex-dev/reflex

Toutes les issues de reflex-dev/reflex

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.