Skip to content

CI and release run the UI tests once - #58

Merged
KnifeLemon merged 1 commit into
mainfrom
ci/ui-tests-once
Oct 12, 2026
Merged

KnifeLemon merged 1 commit into
mainfrom
ci/ui-tests-once

Conversation

@KnifeLemon

Copy link
Copy Markdown
Owner

Since #57, the Windows job runs the UI tests on their own first, with crash and hang blame. The full dotnet test Filee.slnx step that followed ran them a second time.

With one headless application for the whole assembly, the UI tests take about 6.5 minutes on Windows, so the second run added about 6 minutes to every CI run and every release.

Change

  • The full test step in ci.yml and release.yml filters the UI tests out: --filter "FullyQualifiedName!~Filee.App.Tests".
  • A test assembly with no matching tests exits with 0.

The UI tests are still slow on their own: with one application, each test takes longer as the run goes on. That gets its own investigation.

πŸ€– Generated with Claude Code

The UI tests run on their own first (with crash and hang blame); the following full run left them out only in
name and ran them again, about 6 minutes on Windows. It now filters them out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@KnifeLemon KnifeLemon added the build Build and release label Oct 11, 2026
@KnifeLemon
KnifeLemon merged commit edc172c into main Oct 12, 2026
5 checks passed
@KnifeLemon
KnifeLemon deleted the ci/ui-tests-once branch October 12, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Build and release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant