You've already forked Extensions.Configuration.EntityFrameworkCore
Add happy-path tests
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
# RAIC.Extensions.Configuration.EntityFrameworkCore.SqlServer.Tests
|
||||
|
||||
Some basic happy path only tests for functionality exposed by `RAIC.Extensions.Configuration.EntityFrameworkCore.SqlServer.SqlServerNotificationConfigurationReloader`
|
||||
|
||||
## Requirements
|
||||
|
||||
Developers are expected to add their own User Secrets to the test project, containing a default connection string setting
|
||||
(ie. with key `ConnectionStrings:Default`) that points to a pre-configured database that contains a `Settings` table with columns
|
||||
`key` & `value`.
|
||||
|
||||
Additionally, **both** the database and `Settings` table must have change tracking enabled otherwise tests will fail
|
||||
(see the [RAIC.Extensions.Configuration.EntityFrameworkCore.SqlServer README](../RAIC.Extensions.Configuration.EntityFrameworkCore.SqlServer/README.md) for details of how to
|
||||
do this).
|
||||
|
||||
## TODO
|
||||
* Get EF to drop and create the database itself (using `EnsureDeleted()` & `EnsureCreated()`) instead of
|
||||
forcing this on the user
|
||||
* Additional tests off the happy path ()
|
||||
Reference in New Issue
Block a user