Skip to content

test: run T2571 recent-list case serially - #124

Open
nichenqin wants to merge 1 commit into
mainfrom
fix-t2571-serial-case
Open

test: run T2571 recent-list case serially#124
nichenqin wants to merge 1 commit into
mainfrom
fix-t2571-serial-case

Conversation

@nichenqin

Copy link
Copy Markdown
Contributor

Problem

The lab runs cases with it.concurrent (default width 2), but T2571 asserts user-global state: immediately after duplicate, the copy is the first item in the current user's recent-base list.

Run https://github.com/teableio/teable-e2e-lab/actions/runs/33042773544 failed because a concurrent field case visited bsen0JTflQxwELN3sCN after the duplicate and correctly moved it ahead of the copy. This does not reproduce T2571; per-case bases isolate data, not the shared user's recent history.

Change

  • Add optional serial case metadata.
  • Register serial cases with normal it while all others remain it.concurrent.
  • Mark only base-share/a-duplicated-base-in-the-recent-list serial.

Verification

  • pnpm check passes.
  • TypeScript validates all 259 files.
  • No product query/ordering change: a genuinely later user visit must remain ahead of the duplicated base.

Related teable-ee PR: https://github.com/teableio/teable-ee/pull/3194

@CLAassistant

CLAassistant commented Aug 27, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@nichenqin

Copy link
Copy Markdown
Contributor Author

recheck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants