You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2018. It is now read-only.
Confusingly, the utility modules used as examples in this tutorial actually would be a good candidates for mocking, b/c they have so few dependencies, yet the tutorial demonstrates how to load and use actual dependencies in unit tests.
In some cases it's hard to mock all dependencies (like when testing widgets, where the average define() block has about 10+ dependencies from dojo, dijit, esri, etc).
This tutorial may be more useful if it demonstrated how to do one example of testing a widget w/o mocks, and one testing a utility module w/ mocks.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Confusingly, the utility modules used as examples in this tutorial actually would be a good candidates for mocking, b/c they have so few dependencies, yet the tutorial demonstrates how to load and use actual dependencies in unit tests.
In some cases it's hard to mock all dependencies (like when testing widgets, where the average
define()
block has about 10+ dependencies from dojo, dijit, esri, etc).This tutorial may be more useful if it demonstrated how to do one example of testing a widget w/o mocks, and one testing a utility module w/ mocks.
The text was updated successfully, but these errors were encountered: