Isolate the admin end-to-end tests from each other

未关闭
#3,314 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp, sqlite
领域
backend, testing

调研方向

Start with admin/tests/FluentCMS.Admin.EndToEnd/EndToEndHost.cs and BrowserTest.cs to trace how the shared host, SQLite database, users, and sessions are set up. Check the existing end-to-end test classes for shared data and run the suite to identify order-dependent cases. Done means cases pass in any order or alone, and none signs in as a user another case changes.

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

描述

area:admin area:testing type:chore

Problem

The admin end-to-end tests share one published host and one SQLite database per run (admin/tests/FluentCMS.Admin.EndToEnd/EndToEndHost.cs:10,14-18), in a serial collection because tests change its users and sessions (BrowserTest.cs:34-35). Only the browser context is per test. Cases depend on order and timing; #3257 and #3261 each fixed one after it failed.

Proposal

Give each test class its own data: a seed or reset per class, or content types and users named per test, so no case reads what another wrote.

Done together with #3213, which adds cases to the same harness.

Acceptance

  • The cases pass in any order
  • A case run alone passes
  • No case signs in as a user another case changes

Found in the code review of 17 Nov 2026.

主要语言
C#
星标
569
派生
107
平均合并
2 小时 49 分钟
30 天内合并 PR
397

环境准备

从这里开始

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

fluentcms/FluentCMS 的其他 Issue

查看 fluentcms/FluentCMS 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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