mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 22:30:41 +01:00
Update WireMock.Net.AwesomeAssertions to use latest version from AwesomeAssertions #694
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ArminOebb on GitHub (Jun 6, 2025).
Originally assigned to: @StefH on GitHub.
Describe the bug
It seems that the new WireMock.Net.AwesomeAssertions package is still referencing FluentAssertions instead of AwesomeAssertions!
Expected behavior:
WireMock.Net.AwesomeAssertions should only reference AwesomeAssertions, not FluentAssertions
Test to reproduce
public static void HaveReceivedAGetApiCall(this WireMockReceivedAssertions assertions,
string apiBase,
string pathAndQuery)
=> assertions.HaveReceivedACall()
.AtUrl($"{assertions.Subject.Urls[0]}/{apiBase}/{pathAndQuery}").And
.UsingGet();
@StefH commented on GitHub (Jun 6, 2025):
When you look at https://nuget.info/packages/WireMock.Net.AwesomeAssertions/1.8.9
Only AwesomeAssertions is referenced
@ArminOebb commented on GitHub (Jun 6, 2025):
That is how it looks in the dependencies description in NuGet, yes, but in the actual assembly it looks like FluentAssertions is used.
If I use, for example, "dotPeek" to look inside the assembly "WireMock.Net.AwesomeAssertions.dll", you can see, that there is a reference to "FluentAssertions". I don't know why, but that's what the assembly says. If I compile my code it will also say the FluentAssertions is needed.
I also tried to completely remove the WireMock.Net.AwesomeAssertions NuGet package, also from the .nuget/packages directory, and installed it again, but with the same result.
@ArminOebb commented on GitHub (Jun 6, 2025):
Okay, I figured out where it's coming from. Since Version 9.0 the dll of AwesomeAssertions is called "AwesomeAssertions.dll", but in version 8.1 it's called "FluentAssertions.dll". So that's what causes the confusion. Because I referenced AwesomeAssertions 9.0, and WireMock.Net.AwesomeAssertions uses AwesomeAssertions 8.1, where, the assembly, for some reason is called "FluentAssertions". And I didn't reference version 8.1, so that's why there is that compile error with the confusing message that "FluentAssertions.dll" is missing.
So sorry for bothering. Can we hope for a version with the 9.0 AwesomeAssertions lib? :)
@StefH commented on GitHub (Jun 6, 2025):
Using 9.0 should be possible I think.
@StefH commented on GitHub (Jun 6, 2025):
https://github.com/wiremock/WireMock.Net/pull/1309
@ArminOebb commented on GitHub (Jun 10, 2025):
Thank you!