Repository navigation
test: restore when long-running and brittle tests are skipped - #1143
Merged
Merged
Conversation
The TUnit migration swapped the Debug and Release branches and applied the checks to the mock file systems too, so CI skipped the long-running tests everywhere and the brittle tests also against the mocks, which used to run them always. The skip messages pointed to the removed Testably.Abstractions.TestSettings project.
vbreuss
enabled auto-merge (squash)
October 18, 2026 12:55
|
|
This is addressed in release v7.1.2. |
This was referenced Oct 29, 2026
This was referenced Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



The TUnit migration swapped the Debug and Release branches and applied the checks to the mock file systems too, so CI skipped the long-running tests everywhere and the brittle tests also against the mocks, which used to run them always.
The skip messages pointed to the removed Testably.Abstractions.TestSettings project.