Closed timandella closed 1 year ago
Mhm looks like we accidentally created a breaking change on deserialization of json reports pre-testfile support. We should handle that gracefully. Thank you for the report!
On another note, once that's fixed you should be able to see your test results in the report :) 😅
Describe the bug We have a Azure DevOps pipeline that runs dotnet stryker against out unit test project. It ran successfully for version 3.7.1 of dotnet-stryker, but fails with an InvalidOperationException with v3.8.0
The (redacted) command that is being run is this
dotnet stryker -f ../../build/stryker/stryker-config.json --with-baseline:'test/branch' --version 'origin/master' --azure-fileshare-sas "XXX"
Logs The console log shows the following
Expected behavior Stryker to complete without error
Desktop (please complete the following information):
Additional context No error occurs in 3.7.1
I am unable to recreate the error locally (with a Windows 10 OS)
Config file used is as follows: