🐛 Fixture.CreateMany sometimes creates a few bool fields all with false values about autofixture HOT 4 CLOSED

I had the same issue once. It ended up being a type that had a boolean property that offset the procession and making all system under test falling in the order so that the tested property was always in odd/even position.

from autofixture.

Unless otherwise configured, AF alternates true and false values when generating boolean properties (it does something similar with enums too).

If that property needs to be either true or false, it's better if you explicitly configure it to be so.

from autofixture.

Thanks, you are totally right about explicitly configuring a property. But if something works differently on your local pc and in the dev environment it is a bug, am I right?

from autofixture.

Seems the question was answered. Closing the issue.

from autofixture.