Skip to content
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

Strategy for stubbing linked/hidden collections (more globally) #3

Open
zeroasterisk opened this issue Jul 5, 2016 · 0 comments
Open
Labels

Comments

@zeroasterisk
Copy link
Contributor

I know this breaks the idea of unit tests being isolated and mocking all interdependence... but I have had a hard time getting spys/mocks working in Meteor (which is really the core issue to solve)...

In the meantime, this is a great tool for stubbing "the currently scoped" collection to be in-memory only... But I have some methods, which call collection functions, which are not in scope during my testing... is there some way to also stub those other collections somehow? I don't really see how, since ES6 import is encapsulating the collection object for each file.... right?

Recommendations?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants