You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have plenty thorough testing practices for client-side code already; but there's also reasons to test that same code at the command-line:
Coverage support. I can't get code-coverage out of the browser.
Pre-C.I. and server-C.I. support. It'd be nice to have information about server- and client-side test status in one place; and this could be the case with Travis-CI if we PhantomJS-tested the client-side code.
To boot, there's little reason not to. More wide-spread testing is always better.
The text was updated successfully, but these errors were encountered:
I have plenty thorough testing practices for client-side code already; but there's also reasons to test that same code at the command-line:
To boot, there's little reason not to. More wide-spread testing is always better.
The text was updated successfully, but these errors were encountered: