Skip to content
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

Render output in a tree instead of a flat list #2

Open
Raynos opened this issue Dec 27, 2013 · 2 comments
Open

Render output in a tree instead of a flat list #2

Raynos opened this issue Dec 27, 2013 · 2 comments

Comments

@Raynos
Copy link

Raynos commented Dec 27, 2013

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.

@ghost
Copy link

ghost commented Dec 27, 2013

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.

@peteruithoven
Copy link

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 assertions
    t.end();
  });
  t.test('  should show age', (t) => {
    // some assertions
    t.end();
  });
  t.test('  should not show age when not available', (t) => {
    // some assertions
    t.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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants