You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This example includes lots of boilerplate code that is duplicated for every test.
Maybe this example could use constructor/destructor, a base class or a class fixture in order to reduce boilerplate code?
Also, it is not explained why a new instance of the DbContext is used for creating the database schema, seeding the data, and running the tests.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: e4f7b56f-7f91-2f15-1fb6-4f481e97534f
Version Independent ID: 6d9c65c6-f159-b234-48fd-f25da05f0f32
This example includes lots of boilerplate code that is duplicated for every test.
Maybe this example could use constructor/destructor, a base class or a class fixture in order to reduce boilerplate code?
Also, it is not explained why a new instance of the DbContext is used for creating the database schema, seeding the data, and running the tests.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: