Allow managing editors access to featured services and guidance.

They are limited to their own organisation.

https://www.pivotaltracker.com/story/show/76712400
I totally agree that the testing of logic should be pushed down to the level of the code itself, and I think the unit tests you've written provide good coverage there. Where I think we disagree is that the only way to "prove" that your unit tested method is hooked up correctly is to stub and mock its invocation in what is effectively an integration test. That path taken to its logical conclusion quickly lead to mocking/stubbing hell. I've come to believe that stubbing/mocking should ideally be reserved for stuff right at the edges of the system that are outside of our control, and that tests that stub and mock unnecessarily are generally more brittle and make the code harder to change. All we need is a base level of confidence that our code is doing the right thing. Accepted my hastily-written example test isn't quite right, but could it not be adjusted so that it *does* provide a suitable level of confidence that the code is behaving as we want without mocking a method we own?