-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
Problems with moduleForComponent and testing div ID #40
Comments
zigomir
changed the title
Problems if you don't have
Problems if you don't have <div id="ember-testing"></div>
Apr 17, 2014
<div id="ember-testing"></div>
zigomir
changed the title
Problems if you don't have <div id="ember-testing"></div>
Problems with moduleForComponent and testing div ID
Apr 20, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was having problems with testing ember components until I didn't renamed the testing ember app div element's id to
ember-testing
and setApp.rootElement = '#ember-testing'
as well.I looked through the source code and found that
#ember-testing` in it's setup and the container view. I wouldn't change the way it's done right now, but I would at least add some info about it into the readme, so that next me, won't having issues with that.
moduleForComponent
have hardcodedI know same setup is also used in new ember testing guides and this setup info isn't provided as well. Would it be all right if I just add one step into
examples
section and describe that you need those two things to be set up as such?The text was updated successfully, but these errors were encountered: