-
-
Notifications
You must be signed in to change notification settings - Fork 9
Using with QUnit? #3
Comments
+1 |
Due to naming issues with QUnit and Chai, you may need to use as in the import statement. This seems to work for all the use cases you have mentioned.
Sorry for the delay with this. |
@mattmcmanus or @lolmaus let me know if you have issues and I can then update the documentation. |
Hey @jonathanKingston, I've tried it and found a problem: Chai correctly reports failed assertions to QUnit (though the output is far from being expressive), but it does not report successful assertions. They do not appear on the list and do not increment the assertion counter. Even worse, if you only have Chai assertions in a test block, QUnit would report:
|
I suggest a big warning at the top of the README to inform others that this is not compatible with standard ember tests. No qunit compatibility = a bunch of wasted time in vain hopes of incorporating chai yummyness... best of wishes on making this more useful :) |
So I implemented this instead: https://github.com/lolmaus/ember-cli-custom-assertions-collection |
Is it possible to use
ember-cli-chai
with QUnit?If yes, it is confusing how it is supposed to be used. QUnit provides its own
assert
function. Should i not use the QUnit's one? Should i use both? Does Chai'sassert
provide QUnit's features likeassert.expect()
,assert.async()
?Please expand the readme with answers to those questions and some example code.
The text was updated successfully, but these errors were encountered: