That is a nice trick to stub the individual methods. I think it is the recommended way to do that.
I have one example that I think highlights the problem @BlueRaja was describing.
Some things only export functions, like utilities.
I have a utility in my app that I want to stub. A route imports the utility and calls it on the model hook’s resolved data. I’d rather not have my route test also assert behavior from that utility.
I did find that you can stub a given utility with stubbedFunc = sandbox.stub(require(my-app/utils/some-util'), 'default'); That relies upon the dependency loading implementation though, and so would be prone to obscure failures in the future. Because of that, I do not recommend using this in an app.