Well, the proper tool for that would be [Squire.js](https://github.com/iammerrick/Squire.js/), which is designed to mock require.js dependencies. We're [already using Squire in some of our Jasmine tests](https://github.com/edx/edx-platform/blob/master/cms/static/coffee/spec/views/assets_spec.coffee), but for some reason those tests don't play nicely with the tests that *don't* use Squire -- I think that something in the JS execution environment is holding on to the mocks even after Squire tries to remove them. As a result, we're currently running those tests using [a separate test runner](https://github.com/edx/edx-platform/blob/master/cms/static/coffee/spec/main_squire.coffee), which makes for some duplicated code.

I suggest that you give Squire a shot to see if you can easily mock it that way. If you can, great! If it ends up being annoying or requires even more duplicated code, then just go with the solution you've currently got.