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.

Sign up for GitHub

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

Jump to bottom

Document ability to set module-specific resolver #209

Merged
merged 1 commit into from
May 20, 2017
Merged

Document ability to set module-specific resolver #209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,9 @@ displayed in test output. If omitted, defaults to `name`.
* `callbacks` (optional) - an object that may include setup and teardown steps
as well as the other units needed by tests.

* `callbacks.resolver` (optional) - a Resolver instance to be used for the test
module. Takes precedence over the globally set Resolver.

### TestModuleForComponent

`TestModuleForComponent` extends `TestModule` to allow unit testing of Ember
Expand Down Expand Up @@ -79,8 +82,8 @@ Models.

* `getContext` / `setContext` - access the context to be used in each test.

* `setResolver` - sets the resolver which will be used to look up objects from
each test's container.
* `setResolver` - sets a Resolver globally which will be used to look up objects
from each test's container.

* `isolatedContainer` - creates a new isolated container for unit testing.

Expand Down