A test project passes with zero tests, and the CI shards are listed by hand
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with Directory.Build.props:73-76, .github/workflows/ci.yml:90-106, DatabaseServer.cs:90, and SqlServerPool.cs:32-45 to trace the test settings, shard coverage, and existing database template approach. Check how the solution discovers test projects and how PostgreSQL tests create and migrate databases. Done means empty test projects fail, every test project is covered by a shard, and PostgreSQL tests migrate once per run; record the time saved in the pull request. Coordinate with #3267, which changes the same workflow.
Written by the indexing model from the issue text.
Description
Problem
- A test project passes when it runs no tests.
Directory.Build.props:73-76sets--ignore-exit-code 8for every project undertests/, with a comment about stubs that no longer applies. Filtered runs are guarded by--minimum-expected-tests; the unfiltered shards (.github/workflows/ci.yml:90,101-106) are not. - The shard lists are maintained by hand.
ci.yml:90-106names each test project. A new one runs on no pull request and no push to main; only the nightly Windows run picks it up. - PostgreSQL tests create and migrate a database per test.
DatabaseServer.cs:90runsCREATE DATABASEfor each test, and each test migrates it. SQL Server already clones a migrated template (SqlServerPool.cs:32-45).
Proposal
- Remove the ignored exit code.
- A check that every test project of the solution is in a shard.
- Migrate one template database per run and create test databases from it.
Done together with #3267, which changes the same workflow.
Acceptance
- A test project that discovers no tests fails the run
- A test project missing from the shards fails CI
- PostgreSQL tests no longer migrate per test; the time saved is noted in the pull request
Found in the code review of 17 Nov 2026.
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100