-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrations: Improve functional test coverage #1141
Comments
Here are some scenarios I want to cover.
|
Just wanted to know the state of migration functional tests before attacking migrations in PostgreSQL... There seem to be some non-inherited migration tests within each provider's testsuite but nothing comprehensive I can actually use. Should I wait a bit, are there plans to work on this? |
@roji, So far, there are just unit tests to verify the SQL. You can copy these to use in your own unit tests. I also plan to create some provider-inheritable functional tests. I started in bricelam:migtests, but they were way too slow! We have some ideas on how to do it faster, but I haven't gotten around to implementing it yet. |
I've added some basic functional tests that cover the |
Closing. I feel like our coverage is pretty decent now. We'll rely on app building, exploratory testing, and code coverage analysis for more. Creating more provider-agnostic tests will be done as part of #1807. |
Probably by porting existing tests from EF6
The text was updated successfully, but these errors were encountered: