Closed anderswagner closed 4 months ago
the bug happens if you have the same test source files in two different test projects, which is indeed not supported as of today (because nobody though about this situation). This is a legitimate use case, but we need to understand the ramification to support this properly.
I also was hit with this issue, @CptF1nn did you find a way to work around this until it's fixed?
@VMelnalksnis We neded up only using tests for one project against our library instead of multiple sadly
Describe the bug When running stryker with a config using both Api.Test project and Library.Test project, i receive the following exception. Having to dig into the source code of stryker to figure out what could potentially make this error happen is not ideal.
Logs
Expected behavior A more specific error message than an unhandled exception, or otherwise a warning to let the stryker run keep moving forward
Desktop (please complete the following information):
Additional context Stryker config file here, with the same naming:
{ "stryker-config": { "ignore-methods": [ "Arg.NotNull", "Error", "Warning", "Information", "GC.SuppressFinalize", "ConfigureAwait" ], "mutate": [ "!*/Humble.cs" ], "reporters": [ "html" ], "solution": "../X.sln", "project": "X.Library.csproj", "test-projects": [ "../X.Library.Test/X.Library.Test.csproj", "../X.Api.Test/X.Api.Test.csproj"] } }
And the working stryker config here
{ "stryker-config": { "ignore-methods": [ "Arg.NotNull", "Error", "Warning", "Information", "GC.SuppressFinalize", "ConfigureAwait" ], "mutate": [ "!*/Humble.cs" ], "reporters": [ "html" ], "solution": "../X.sln", "project": "X.Library.csproj", "test-projects": [ "../X.Library.Test/X.Library.Test.csproj"] } }
The same sort of setup has worked for other projects (Api.Test & Library.Test)