Allow managing editors access to featured services and guidance.

They are limited to their own organisation.

https://www.pivotaltracker.com/story/show/76712400
I should perhaps be clearer about what this test is intended to do.

The point of stubbing is to push the testing of logic down to the same level as the code itself, and for the same reasons, to avoid filling higher-level tests with lots of noise.  The idea is to have proven edge-case behaviour before you get to the acceptance tests, which in this application is Cucumber.

The other side of this coin is proving that the unit-tested functionality is actually hooked up.  You can't do that with a happy-path real-world test because that could be covered by simpler code in the view (or wherever).  You're not proving that the unit tests you used for fast combinatorial testing are fully covering the actual interaction of the site.

Stubbing allows this by tying the behaviour (in this case visibility of services and guidance) to a specific method invocation which has been thoroughly tested elsewhere.