@RedDeath,
thanks for your comment.
I didn’t really mean to use this approach on production. That’s why I wrote, that the only usage on production I would consider (as I know some people use it) is to compile such Unit Tests project into an executable and run it when your application is installed for the first time – to have database structures initialized. However, I don’t think I’d personally use that on production 🙂

This approach is great during development phase – as least I found it useful for that purpose.

context.Database.EnsureCreated();

is NOT compatible with Migrations, so I would be very careful of using this on production.
First deploy will go fine, but after that…