Customizations are ignored

I’ve recently updated from AutoFixture 3.50.2 to 4.11.0

After update, Customize<>() is not used when creating object with Build()

One more thing, probably related. When there are multiple customizations on the same object, only the last is valid, and previous are ignored. (The quick fix is to chain them inside one block, but this should not be the final solution.)

See the reproductions for both issues:

using AutoFixture;
using Xunit;

namespace CustomizationDoesntWork
{
    public class ProofTest
    {
        public class Example
        {
            public string Name { get; set; }
            public string City { get; set; }
        }

        [Fact]
        public void ShouldUseCustomizationWhenBuilding()
        {
            var fixture = new Fixture();

            fixture.Customize<Example>(e => e.Without(p => p.Name));

            var exampleByCreate = fixture.Create<Example>();
            Assert.Null(exampleByCreate.Name); // ok

            var exampleByBuild = fixture.Build<Example>().With(e => e.City, "something").Create();
            Assert.Null(exampleByBuild.Name); // fails!
        }

        [Fact]
        public void ShouldRememberAllCustomizations()
        {
            var fixture = new Fixture();

            fixture.Customize<Example>(e => e.With(p => p.Name, "John"));
            fixture.Customize<Example>(e => e.With(p => p.City, "New York"));

            var exampleByCreate = fixture.Create<Example>();
            Assert.Equal("John", exampleByCreate.Name); // fails!
        }
    }
}

[Kralizek]

@aivascu I don’t work for @emgdev anymore but I suppose the new CTO (@simgu) will assign the edit to someone else.

Anyway I have cloned and republished the guide on my own company’s account:

Repo: https://github.com/insight-architectures/unit-testing-csharp/ Published version: https://docs.insightarchitectures.com/unit-testing-csharp/

EDIT:

@ecampidoglio created an issue here and I cloned it in my repo

[elonmallin]

Thanks @ecampidoglio =)

Somehow I found these two misleading things pointing in the same direction before the docs xP

Anywho, my use case wouldn’t be solved even if this worked, I’d also need a callback on Create, similar to https://github.com/AutoFixture/AutoFixture/issues/988.

Then building test data for EF Core InMemory testing would be quite nice:

// Setup
var fixture = new Fixture();

fixture.Customize<Person>(b => b
    .With(p => p.Id, () => UniqueId())
    .OnCreate((person) => {
        _efCoreInMemoryTestContext.Persons.Add(person);
        _efCoreInMemoryTestContext.SaveChanges();
    })
);

// Test
// Arrange
var person = fixture.Build<Person>()
    .With(p => p.UpdatedDate, DateTime.Now.AddDays(-8))
    .Create(); // Person has a generated id, is saved to the InMemory DB and is ready to use in EF Core InMemory testing.

// Act
// Get persons updated more than a week ago

// Assert
// Result matches person