You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
using Testcontainers.CosmosDb;
using WireMock.Net.Testcontainers;
await new WireMockContainerBuilder()
.WithAutoRemove(true)
.WithCleanUp(true)
.Build()
.StartAsync();
await new CosmosDbBuilder()
.Build()
.StartAsync()
.ConfigureAwait(false);
The text was updated successfully, but these errors were encountered:
StefH
changed the title
WireMock 1.5.46 is incompatible with TestContainers 3.7.0
WireMock.Net 1.5.46 is incompatible with TestContainers 3.7.0 (2)
Jan 24, 2024
StefH
changed the title
WireMock.Net 1.5.46 is incompatible with TestContainers 3.7.0 (2)
WireMock.Net 1.5.46 is incompatible with TestContainers 3.7.0 (issue 2)
Jan 24, 2024
Describe the bug
When using another TestContainers Module that relies on Testcontainers 3.7.0, WireMock container throws an exception.
Program.cs
this code fails throws exception
when the csproj is
the exception is not thrown when I downgrade Testcontainers.CosmosDb to 3.6.0.
Expected behavior:
On nuget (https://www.nuget.org/packages/WireMock.Net.Testcontainers#dependencies-body-tab) states atleast 3.6.0 TestContainers https://www.nuget.org/packages/Testcontainers/) (>= 3.6.0) so I would expect it not to throw an exception when I upgrade the other module to 3.7.0
Test to reproduce
Create a new console application
add the following to .csproj
Program.cs:
The text was updated successfully, but these errors were encountered: