I am using mocha, chai, sinon, and squire to unit test some Backbone.JS Views and Models. Everything works beautifully, until I hit a JS module that uses a relative path. For example, a View under test may request a resource image located in a resource file relative to that View's file. Mocha, however, causes the request to be relative to the test file that is calling it.
So if I have a test file myProject/test/im-a-test.js that is probing a source file myProject/src/views/im-a-view.js which uses resource myProject/rsrc/im-an-img.png, I get a file not found error because it is looking for myProject/test/rsrc/im-an-img.png, which of course does not exist.
I cannot change the source code currently, and am looking for a way to trick the test into providing the correct path to the module. Does anyone know how to do this, maybe with some sort of path stub or mock?
The file structure also must remain in tact, so "put im-a-test.js in myProject/src/views" is not a solution.
Note: This may be somewhat similar to this question. I couldn't get the solution there to work for my situation, but maybe that could trigger some ideas.