Old docs

Version 3.2.0 documentation links

This document has links to documentation for the EfCore.TestSupport, version 3.2.0.

• Helpers to create a Sqlite in-memory database for unit testing

• Helpers to create connection strings with a unique database name (via appsetting.json)

• Helpers for creating unique SQL Server databases for unit testing

• Helpers for creating unique SQL Server databases for unit testing

• Helpers to create Cosmos DB databases linked to Azure Cosmos DB Emulator

• Ways to make sure your database has an up-to-date schema and is empty

• Various tools for getting test data, or file paths to test data

• A tool for applying a SQL script file to a EF Core database

• Tools for capturing EF Core logging

• EfSchemaCompare, a tool for people using SQL scripts to migrate their database

  • How to use
  • Configuration
  • Limitations

• Seed from Production

  • 1a. Extract stage
  • 1b. Anonymization
  • 2. Seed stage
  • Using with DDD

• xUnit Fluent Validations

Notes on running unit tests

Running in NET Core

In NET Core the EfCore.TestSupport features work when running the unit tests via Visual Studio Test Explorer, or any other test runner such as Resharper.

Running in NET Framework

In NET Framework, by default, EfCore.TestSupport methods that accessing files or appsettings fails when running via Visual Studio Test Explorer (but resharper works). This is because the NET Framework XUnit runner defaults to using a shadow copy. The solution is to add a XUnit configuration file to turn off the shadow copy. I have added a project called Net472Test to test this and you can find my XUnit xunit.runner.json file here that provides the correct setup. NOTE: read the XUnit config docs as you need to set the file properties for it to work.