-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warn or error when stubbing non-existent functions #234
Comments
Possible? Yeah. It feels like two things are in conflict here. If you want to use It's going to be tricky to shoehorn this into the current API but I'm happy to hear any thoughts if you have them on how we might do it. |
This is great tool for writing my tests, however I've noticed that both with and without
noCallThru()
, if we stub a library and write out our test cases, if the underlying module methods then change, our test cases continue to work, even though the underlying methods have changed. The running code would obviously break, but the tests seems to behave just fine.Would it be possible to warn or even fail when stubbing functions on
require()
'd modules that don't actually exist?The text was updated successfully, but these errors were encountered: