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
The goals of TAP and tape are great, but an alternative would be nice for a number of reasons:
TAP is difficult to work with
Bad experience for humans out of the box
TAP formatters don't work that well, especially when regular stdout and tests are mixed
tape requires a bunch of Node.js built-ins (fs, Buffer, process)
Bundling these for a browser test environment is simply unacceptable
Tape is generally more bloated and complex than needed.
The tape interface is not oriented around async/await
A replacement should be implemented while preserving the following desirable qualities from tape:
Not require any special test runner (i.e. running tests directly via Node.js should work fine)
Works fine in Node.js and browsers
Optional, nice machine-readable test output.
Fortunately, the Chrome Remote debug protocol provides a mechanism to imperatively trigger a different logging mechanism for when a test runner wants to do fancier output.
The goals of TAP and tape are great, but an alternative would be nice for a number of reasons:
fs
,Buffer
,process
)A replacement should be implemented while preserving the following desirable qualities from tape:
Fortunately, the Chrome Remote debug protocol provides a mechanism to imperatively trigger a different logging mechanism for when a test runner wants to do fancier output.
API example
The text was updated successfully, but these errors were encountered: