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
When faucet is run with a list of files or on a directory this could be made to work, but TAP doesn't have a standard way of differentiating which file a test was declared in.
Are subtests parsed to TAP as something you can use in Faucet? Example with tape:
test('Card component',(t)=>{t.test(' should show header',(t)=>{// some assertionst.end();});t.test(' should show age',(t)=>{// some assertionst.end();});t.test(' should not show age when not available',(t)=>{// some assertionst.end();});t.end();});
Having a tree generated based on files would be great too, but this would only work with specific runners. I'm assuming?
We have a fantastic divider to structure test output in a tree.
It's files.
We could group the list of green ticks by which file the
test('...')
occur in.The only problem is I'm not sure how to place file meta information in tap output or when calling
faucet
from the cli directly.The text was updated successfully, but these errors were encountered: