Error reporting

[kevva]

Should show the err.stack for each failed test imo. Also, we need to sort out the error messages some I think.

[sindresorhus]

👍

[kevva]

Renamed since error reporting etc will happen in a reporter. Let's convert the output to be TAP compliant first.

[sindresorhus]

I don't want TAP output as default as it's quite limiting and annoying to work with. I definitely want to support it, but the default reporter should be something nice and simple. My thought was to have a hard-coded reporter and a TAP option, but no reporter option, as TAP has a gadzillion reporters and it might be a good idea not to reinvent the wheel. Thoughts?

[kevva]

Hm, yes I agree that it shouldn't be used as default (for the user), but maybe just under the hood. My thought was having it always write TAP output but use a default reporter, looking like the one we use now, if nothing else is specified.

[sindresorhus]

Having to depend on the TAP output for our default reporter limits what we can do. I honestly see no benefit of doing that. We can easily support TAP too, but I would prefer our default reporter is more tightly coupled so we can make it really good. So good most people won't need another reporter.

[kevva]

Alright, that makes it a little easier too :). Let's focus on getting everything else to work nicely first and add TAP support later on.

[sindresorhus]

Yup, let's build what we need first and make it stable. I've honestly never needed another reporter. We can add bloat like that later on like you said.