Refactor Test Suite #8
Description
Currently I've been mapping a lot of the test suite from the original code, but it's quickly getting unwieldy, and unclear on what should live where.
My current thoughts are to make the tests that integrate with the dummy_app all be purely integration tests, going through a maximum feature set application (load all the things, make sure they work in concert). The unit tests would be then purely under the sorcery folder, using a more direct class mocking approach.
That being said, having the tests be 1:1 with the file structure would lead to absolutely gigantic specs, so I'm open to any ideas on how to logically break up the unit test structure further. I want to make it really clear for developers coming in where they should be looking for a spec, and not hide tests behind too much abstraction.