Closed BrunoRM closed 3 years ago
The problem are related to a specific test that was using Faker (from bogus lib) in a MemberData test theory. The MemberData looks like this:
public static IEnumerable<object[]> Test_Data = new List<object[]>
{
new object[] { new Faker().Random.String(1) }
}
After some tests I figured out that when new Faker()
is removed (and replaced simple by a string with length 1), stryker runs the mutation tests successfuly.
Sounds like a bug with the dynamic test cases detection, thank you for reporting! I see that you reported that the bug is fixed in the rc release, thank you for checking!
Apparently is a problem with the instantiation of Faker inside of MemberData. We have some other tests that uses MemberData without Faker, and Stryker can run it successfully.
Yes, after the Stryker upgrade to 1.0.0-rc3 the tests pass and reports is generated correctly, so seems that the bug is fixed.
Describe the bug I'm trying to run mutation tests in my local environment and in Azure Pipelines, both throws an exception and exits with error. The exception description is:
Doing a checkout to previous commit before the feature I implemented, tests executes successfuly, with my changes, it starts to break.
Logs VsTest-log.txt log-20211027.txt
Desktop (please complete the following information):
Additional context I upgraded Stryker to version 1.0.0-rc3 in my local machine and it works. But i can't do this in the pipeline now.
Another logs that I see on start of the run is:
This "Fail to load assembly" error can contribute to the test execution error? This same logs is present in the run of previous commit that I mentioned, and not affected the execution.
Can anyone help on how to solve this problem?