Update Expecto to 10.2.3 #2874
Merged
Update Expecto to 10.2.3 #2874
Conversation
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
Numpsy
commented
Oct 24, 2025
Test Results 12 files 12 suites 33m 6s ⏱️ Results for commit 329340d. ♻️ This comment has been updated with latest results. |
xperiandri
approved these changes
Oct 25, 2025
And Expecto.FsCheck and the test adaptor to the matching versions.
xperiandri
force-pushed
the
expecto_up
branch
from
388b6cb to
329340d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
And Expecto.FsCheck and the test adaptor to the matching versions.
Description
This was originally a plan to break out a bit more of the .NET 8 PR into a self contained change and to pick up an optimization I made to Expecto to speed up test discovery, but when doing it I noticed that the existing change in #2818 is also disabling the timeouts that have been applied to the test runs, so this version tries to do the update whilst retaining those.
The Expecto dependency here should be internal to the unit tests, so it shouldn't have a public effect in the Fake modules (The Fake.DotNet.Testing.Expecto module doesn't depend on Expecto itself)