-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support registering a custom assertion module #25
Comments
Yes you can. Updated the readme about it: 3deba51 It won't work with planned assertions though. For that, we'll need an AVA method that hooks the assertion methods in the assertion module you supply so that it can do the assert counting. Shouldn't be that hard, but not top priority. |
Thanks. Any tutorial on how to do that? Code sample will be cool. |
How to do what? With assert counting is not possible yet as outlined above. Without assert counting is documented in the readme as already mentioned. |
Please read the discussion in #49 before commenting. We should support any assertion library, but have built-in "adapters" for the most popular ones. By "builtin adapter", I mean users can just pass the instance (e.g. |
I think we've become quite comfortable with AVA's built-in assertions since this issue was raised. We won't be adding tight integration for other assertion libraries any time soon, so I'm closing this issue. |
People can already use their favorite assertion module with AVA. It just won't work with planned assertions. That being said, I almost never use planned assertions anymore, now that we have async/await. |
How to use it? For example, Chai is very nice. Or assert.js
The text was updated successfully, but these errors were encountered: