@klamping I can't provide a 100% complete answer for that.

I do like the idea of mocking as much as possible, but if we were to do that we'd need some kind of check that would ensure that the mocks match what the real world is presenting us, and that kind of maintenance is the kind that (I assume) not many people would want to own.

I'd like to hear what the problem with injecting `rxEnvironment` is in this case. Is it not properly leveraging ngMock or something?