Version 5 Roadmap

[aivascu]

Hello everyone,

AutoFixture v5 development is currently in progress and first releases have been published, on the MyGet feed NuGet feed. This thread will collect information on the planned and implemented features as well as deprecated features in the upcoming version.

If you have any ideas please share them, in the Discussions.

The list below is incomplete and subject to change.

✨Features

AutoFixture

• Add support for .NET Standard 2.1 ✨ Add support for .NET Standard 2.1 #1324
• Add support for IAsyncEnumerable<> ✨ Add support for IAsyncEnumerable<> #1325
• Add NET 5 target to all projects Added .NET 5 target runtime #1443
• Add NET 6 target to all projects Added .NET 6 time structs #1453
• Add support for IAsyncEnumerator<>
• Add support for record types
  • Add support for init accessors
  • Add postprocessor API for constructor parameters
• Improve support for value objects

AutoFixture.NUnit3

• Allow [Frozen] to be used for injected test parameters
• Add [MemberAutoData]
• Add [ClassAutoData]

AutoFixture.NUnit4

• Migrate existing library
• Update AutoData attibutes (see NUnit 3 changes above)

AutoFixture.XUnit2

• Allow [Frozen] to be used for injected test parameters Reimplemented XUnit 2 AutoData attributes #1433
• Fix [MemberAutoData] Reimplemented XUnit 2 AutoData attributes #1433
• Add [ClassAutoData] Reimplemented XUnit 2 AutoData attributes #1433

AutoFixture.NUnit2

• Enable running tests using dotnet test

AutoFixture.AutoMoq

• Raise minimum supported Moq version to v4.7.49 for netstandard1.5 or greater

AutoFixture.Idioms

• Fix EmptyGuidBehaviorExpectation not throwing on ArgumentException
• Skip nullable parameters in GuardClauseAssertion ✨ Skip nullable parameters when doing GuardClauseAssertion #1328
• Add assertions for equality operators

⚠️Deprecations

AutoFixture.*

• Drop support for .NET Core 1.x
• Drop support for .NET Standard 1.x
• Raise minimum .NET Framework version to v4.6.1
• Raised minimum supported version of NUnit to 3.7.0 Added .NET 5 target runtime #1443
• Raised minimum supported version of xunit.extensibility.core to 2.2.0 Reimplemented XUnit 2 AutoData attributes #1433
• Raise minimum supported version of FakeItEasy to 6.0.0 Dropped vulnerable package dependencies #1429
• Raise minimum supported version of Moq to 4.7.49 Dropped vulnerable package dependencies #1429
• Raise minimum supported version of Foq to 1.8.0 Dropped vulnerable package dependencies #1429
• Raise minimum supported version of FsCheck to 2.14.0 Dropped vulnerable package dependencies #1429
• Raise minimum supported version of NSubstitute to 3.0.0 4.0.0 Dropped vulnerable package dependencies #1429
• Raise minimum supported version of System.ComponentModel.Annotations to 4.4.0 Dropped vulnerable package dependencies #1429
• Raise minimum supported version of FSharp.Core to 4.2.3 Dropped vulnerable package dependencies #1429
• Replace .NET Framework assembly reference to System.ComponentModel.DataAnnotations with package reference Dropped vulnerable package dependencies #1429
• Drop support for AutoFixture.RhinoMock
• Drop support for AutoFixture.NUnit2
• Drop support for AutoFixture.XUnit1
• Hide/Remove [Obsolete] API marked as error
• Mark as error, non-error [Obsolete] API

[rcdailey]

Does supporting record types imply support for init-only properties? At the moment there's no good mechanism to initialize a record type's init-only properties. This probably stems from the existing struggles with proper constructor support, especially with the use of a mocking framework via AutoData.

[aivascu]

@rcdailey actually I am planning to do both, support for init accessors and an improved API for constructor parameters. However if the implementation will drag for too long I might move it to v6.

[Kralizek]

Should we also consider updating:

• up .net framework support to version to 4.8 (currently we support 4.6.1 which has reached EOL
• up current .net sdk to 6.0.100 with rolling forward for minor version (currently in v5: 5.0.401 with no roll forward configured)

{
  "sdk": {
    "version": "6.0.100",
    "rollForward": "latestMinor"
  }
}

[eduarrodrigueztb]

Hi Thank you for this awesome library, Is the AutoFixture library still in development? I see this V5 comments are from 1 year ago so not sure if the development somehow stopped ?

[isberg]

@eduarrodrigueztb there definitely seems to be progress towards V5. A new pre-release version was made available on nuget this morning. I believe heroic efforts are made on very limited time.