Possible improvements to how we test Memorious #199
Description
Currently the bulk of the testing we do in Memorious is based on mocking the interface of various functions to perform the tests. Often this doesn't test the expected output; instead we check whether the mocked function was called with the expected input or not. This is not super useful in preventing breakage.
Instead of using mocks, we could run a set of small crawlers against a fixed set of web pages built to test various Memorious operations. And we should check whether the output produced by the test crawlers matches the expected output or not. These end-to-end tests should make our testing suite more robust and we shouldn't need to use mocks to test functionality where unit testing is hard to do.