CI skips the Windows adapter tests and fuzz campaigns; build docs have drifted #54

Open
opened 2026-11-11 00:15:30 +00:00 by james.maes · 0 comments
Owner

The Gitea build runs the core tests only. The adapter tests in the UiTests assembly (files, watcher, registry) and the seeded fuzz campaigns never run on a push.

Also:

  • The coverage gate accepts a package with no measured lines, and a report left by an earlier run on the host runner can decide the result.
  • The core project locks an SDK tool package that only a command-line head would need; there is no such head, and the entry breaks locked restore when the SDK patch level changes.
  • CLAUDE.md, DEVELOPERS.md and CONTRIBUTING.md give different test commands from CI and describe checks that no longer run anywhere.
  • RELEASING.md does not say that a tag currently publishes nothing.
  • Test temp folders and the test registry parent key are left behind.
The Gitea build runs the core tests only. The adapter tests in the UiTests assembly (files, watcher, registry) and the seeded fuzz campaigns never run on a push. Also: - The coverage gate accepts a package with no measured lines, and a report left by an earlier run on the host runner can decide the result. - The core project locks an SDK tool package that only a command-line head would need; there is no such head, and the entry breaks locked restore when the SDK patch level changes. - CLAUDE.md, DEVELOPERS.md and CONTRIBUTING.md give different test commands from CI and describe checks that no longer run anywhere. - RELEASING.md does not say that a tag currently publishes nothing. - Test temp folders and the test registry parent key are left behind.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/MarkdownViewr.Windows#54