Class per route+method

I tend to prefer resetting to a known state before a test in a `setUp`, as opposed to relying on `tearDown`. The reason being is that, if you rely on `tearDown`, you end up having to rely on every single test coming before you to `tearDown` correctly. In other words, if you are relying on some `tearDown`, and it's not being executed, it can be extremely hard to pinpoint which test is causing the erractic behavior or even what the issue is.

That said, `tearDown` can still be useful.