Move the integration test suite to Playwright

未关闭
#7,617 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, playwright, python
领域
ci-cd, testing, web-dev

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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)
主要语言
Python
星标
29k
派生
1.8k
平均合并
2 天 22 小时
30 天内合并 PR
143

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

reflex-dev/reflex 的其他 Issue

查看 reflex-dev/reflex 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。