The core unit tests use EF Core's InMemoryDatabase for testing, but that does not seem to be possible with the MVC example site (specifically the Identity DB context). So the MVC Example site is running using LocalDB. While the database is not committed to the repo, it does not get recreated each time the site runs, or when the Selenium tests run, so tests could fail after the first time it is run (without manually removing the old database). Not sure the best way to solve this problem...
The core unit tests use EF Core's InMemoryDatabase for testing, but that does not seem to be possible with the MVC example site (specifically the Identity DB context). So the MVC Example site is running using LocalDB. While the database is not committed to the repo, it does not get recreated each time the site runs, or when the Selenium tests run, so tests could fail after the first time it is run (without manually removing the old database). Not sure the best way to solve this problem...