-
Notifications
You must be signed in to change notification settings - Fork 12
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
Testing Library #99
Comments
I am partial to Mocha or Jasmine. I also know QUnit very well. I know nothing of Jest in fact never heard of it. I might assume other JS devs know less of Jest then Jasmine or QUnit. |
An advantage for Jasmine over both Mocha and QUnit is that Jasmine comes with its own mocking API while Mocha and QUnit would require Sinon to fill that need. Also Jasmine and QUnit comes with their own assertion API where Mocha would also needs something like Chai to fill that need. |
FWIW, We use karma with jasmine and headless chrome at Continuity.
…On Tue, May 15, 2018 at 3:48 PM Devin Weaver ***@***.***> wrote:
An advantage for Jasmine over both Mocha and QUnit is that Jasmine comes
with its own mocking API while Mocha and QUnit would require Sinon to fill
that need. Also QUnit comes with an assertion API where Mocha also needs
something like Chai to fill that need.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#99 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAETVPEyl6C4o3AOVELZPj9v2qZOrMveks5tyzEBgaJpZM4T5E6s>
.
|
Now that things are going swimmingly and we can build the site again, lets get back to the real winner, testing.
Do you guys have a JS test framework of choice for unit tests? I'm partial to Jest, because I come from the react world where Jest is the standard, but I am open to others if people have strong opinions.
The text was updated successfully, but these errors were encountered: