-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
use should() with chai #14
Comments
Aha ... putting into test-helper.js works:
|
Glad you sorted it. Did you mean Because the blueprints all use |
chai.should needs to be called once globally in order to inject "should" into Object.proto. Having this available doesn't preclude the use of
in all their tests.) I at least haven't hit any drawbacks or collisions with having .should everywhere. In the best case, availability of should would be configurable somehow. Is EmberENV available here? |
btw also using sinon -- found http://knomedia.github.io/blog/2014/05/31/using-ember-cli-and-sinon/ helpful for install, but is a bit of a winding path. Could there be blueprints for "install some (arbitrary) test package"? |
@shaunc you could also use: https://github.com/csantero/ember-sinon |
👍 to exposing Chai internals in each test (which seems to be the way ember-cli is suggesting to write qunit tests). Personally for me assert has the most sane syntax as for BDD code a real BDD assertion library should be used external to these tests where by business can drive the tests like cucumber. So I would like to be able to do:
Or similar. |
So, we've just introduced a To semi-officially support We could also export |
This should be covered by ember-cli-chai now. |
I'm having trouble using should() with chai -- can't seem to import it? Could you add to the doc? Also, if we want to globally initialize chai.should(), where should the code go?
The text was updated successfully, but these errors were encountered: