From 6186a040c68250ba6b7130365f15ed9003fc7492 Mon Sep 17 00:00:00 2001 From: Matthew Nguyen Date: Thu, 6 Aug 2015 13:43:34 -0700 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ec094c91..e6252cca 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ Unit tests have the advantage of giving you direct access to the component insta - You have access to the component instance through `this.subject()`. - If you want to render the componenet's template, call either `this.render()` or `this.$()`. - Testing the component's template is through `this.$()`. -- You are required to specify any dependencies other than the component's template in the `needs: []` option. This includes helpers, services, partials, and any other componenets (with their templates) that are referenced. +- You are required to specify any dependencies other than the component's template in the `needs: []` option. This includes helpers, services, partials, and any other components (with their templates) that are referenced. - Unit tests do not call most of the Ember lifecycle hooks. `didInsertElement` and `willDestroyElement` will be called, but the remaining hooks introduced in Ember 1.13.x will not be. - There is no outer context for the component so testing things such as actions will require directly stubbing the actions on the component.