V5.2.0

This release supports both EF Core 5.10 and EF Core 6.0 and is an update the the 5.1.0 to fix a few problems and naming conventions.

• BREAKING CHANGE from 5.1.0: changed CreatePostgreSqlUniqueDatabaseOptions to CreatePostgreSqlUniqueClassOptions to match other usages
• Extra checks on the length of the PostgreSQL database as there is a 64 char limit
• Also improved the PostgreSQL EnsureClean code to make it easier for testing migrations in your tests

V5.1.0

New release to add support to EF Core 6. Changes are

• BREAKING CHANGE: Renamed DeleteAllUnitTestDatabases to DeleteAllSqlServerTestDatabases
• REMOVED obsolete methods: ...OptionsWithLogging (use ...OptionsWithLogTo), CreateEmptyViaWipe (use EnsureClean)
• NET6 Support: Updated to support both EF Core 5 and EF Core
• New Feature: Added PostgreSQL database helpers, including EnsureClean (see docs)
• Feature: Reinstated the Seed Database feature to this version due to requests from users

V6.0.0-preview001

6.0.0-priview001

• Updated to Net6-rc.2 preview
• Added PostgreSQL database helpers
• Added the Seed Database feature back in at request of users

V5.0.0

• A serious cleanup to the this library with BREAKING CHANGES
• BREAKING CHANGES
  • Altered SqliteInMemory methods to return a IDisposable options (disposes connection at the end of the test). THIS WILL BREAK YOUR CODE.
  • Cosmos DB methods renames and extended
• REMOVED FEATURES
  • Removed EfSchemaCompare - its in its own library, EfCore.SchemaCompare.
  • Removed SeedDatabase - use old 3.2.0 EfCore.TestSupport version
  • Removed InMemory Database helper - use EF Core's In Memory database
• New features
  • Add EnsureClean. This clears the schema and data and set up new model (only for SQL Server)
  • SqliteInMemory now has CreateOptionsWithLogTo extension method
  • SqlServer now has CreateUniqueClassOptionsWithLogTo and CreateUniqueMethodOptionsWithLogTo extension methods
• Marked as obsolete
  • CreateOptionsWithLogging<T> - use ...ToLog version
  • CreateUniqueClassOptionsWithLogging<T> - use ...ToLog version
  • CreateUniqueMethodOptionsWithLogging<T> - use ...ToLog version
  • CreateEmptyViaWipe - recommend EnsureClean or respawn

NOTE:It is no longer possible to detect the EF Core version via the netstandard so now it is done via the first number in the library's version. For instance EfCore.TestSupport, version 5.?.? works with EF Core 5.?.?.

Version 3.0.0 - supports EF Core >=3.0 (as well as EF Core >=2.1)

V3.0.0

Version 3.0.0 release - supports EF Core >=2.1 and >=3.0

Version 2.0.0

Various added features and bug fixes. Contains small breaking changes. See ReleaseNotes for more information.

Better capture of EF Core logging output

See Capture EF Core logging in project's Wiki for how it works.

NET Core 2.1 version

V1.4.0

Setup for 1.4..0 release

V1.3.0

The main change is I have fixed some bugs in the TestData class (used for loading test data) and also made it os-agnostic, i.e. the TestData methods should now work on Mac and linux (thanks the Henrik Blick for pointing this out).

I have also added a ReleaseNotes.md file to the top level which lists all the changes

V1.2.0

BREAKING CHANGE: The SqlServerHelpers, SqliteInMemory, and EfInMemory option setting extensions now default to throwing an exception if a Microsoft.EntityFrameworkCore.Query.QueryClientEvaluationWarning is logged. I have done this because I consider this warning a sign of poor performing code.

Please rerun your unit tests. If any fail then the shown line contains EF Core code that logs a QueryClientEvaluationWarning. You can suppress this by setting the throwOnClientServerWarning property in the options build method to false. However, I would suggest you look at the EF Core query that caused the error and consider altering the LINQ such that it can be turned into code that runs in the database.