Changing require result instead of variables about rewire HOT 3 CLOSED

Yes, I see the advantages. It's more likely to change a variable name than the dependency.

But I think your suggestion is impossible to implement because rewire does no static analysis of your code. Thus it doesn't know which variables are referencing which module. The only way to accomplish this is by mapping the dependency-paths on module startup like node-sandboxed-module does:

var foo = rewire("./foo.js", {
    "./util.js": utilMock
});

But if your prefer this approach I think it would be better to just use node-sandboxed-module 😉.

Personally I came to the conclusion that after all unit-tests are usually gray-box-tests. Basically you are aware of the implementation but you're trying to test it like you didn't know. If you're changing the implementation you'll likely need to adjust the unit-test as well.

I like your idea, but I don't know how to implement it.

from rewire.

Okay, thanks for your answer. Too bad I can't have the best of rewire and sandboxed-module. I think I'm gonna stick with rewire either way since I really like the non-eval approach :)

Interesting about the gray-box-testing. Never thought about that in that way, but I guess it makes sense.

from rewire.

Nevermind, it's always good to discuss about improvements 👍

from rewire.