Release 0.5.1

What's Changed

• Bugfix - Connectionstring issue when not specifying database name by @carl-berg in #8

Full Changelog: adatabasefixture-0.5.0...adatabasefixture-0.5.1

Release 0.5.0

This release has removed the helper libraries:

• ADatabaseFixture.SqlServer, which is no longer needed since the class SqlServerDatabaseAdapter now uses a connection factory, which removes the dependency on Microsoft.Data.SqlClient. This class has since been moved into the core package.
• ADatabaseFixture.GalacticWasteManagement, this package has been deprecated since GalacticWasteManagement has been deprecated.
• ADatabaseFixture.FluentMigrator, this package has been removed since creating your own migrator implementation is simple enough.

Now that the helper packages have been removed, consumers a now required to implement their own fixture migrators. This puts a little bit of extra work on the developer, but reduces the risk of incompatibility where the user might want to use a newer or older version. The Readme file has been appended with instructions on how to implement migrators for

• ADatabaseMigrator
• EfCore Migrations
• FluentMigrator

Release 0.4.1

Upgraded Microsoft.Data.SqlClient to version 5.1.4 and FluentMigrator.Runner to version 5.0.0 in #4

Release 0.4.0

• Changed the connection abstraction from IDbConnection to DbConnection in #3
• Tweak to how existing connections to the database are dropped at the end or start of a new test suite

Release 0.3.0

Made creation, migration and removal of database asynchronous.

In prior versions, the database was created and migrated in the DatabaseFixture constructor and the database was removed in the dispose method.

In the new version the DatabaseFixture instead has two methods InitializeAsync and DisposeAsync to create and remove the database. These methods also happen to match the xUnit interface IAsyncLifetime, which the DatabaseFixture class should implement if you use xUnit for tests.