Refactor unit tests to use mocks instead of a database #17
Testing against an actual database presents several problems, foremost of which are
While using mocks does not provide a comprehensive test (LINQ-to-Objects has some different behaviors than using LINQ w/ the Entity Framework) it can still provide a quick check of application logic.
Colleges should provide their own college-specific tests, against an actual database, in addition to the mocked tests provided.
Confirmed that no existing unit tests (against the database) fail due to the EF 6 upgrade (2 failed due to unexpected data, 1 timeout) - after adding the following line to the top of
// Disable default initializer, which tries to modify the database when this method runs. Database.SetInitializer<OdsContext>(null);
I did not commit or push the new code to the main repository.