Standardize errors in API

[vadimdemedes]

Currently, errors array of API instance contains exceptions, rejections and failed tests. As a consequence, items can be different from one another and we have to detect what's what in a loop.

We need to standardize the items in errors array, so that it's easily "forEachable" and all items have the same properties.

[jamestalmage]

👍

[sindresorhus]

👍

[ariporad]

@sindresorhus, @jamestalmage, @vdemedes: How would you want this implemented? Should everything just get wrapped in an error? A promise? A custom object?

[vadimdemedes]

I haven't thought about that yet, but every item in errors should have the same set of properties, so that we can easily output the list of errors at once. So, whether it's a failed test or uncaught exception (which does not have a test assigned to it), the error object should have the same props.

[jamestalmage]

Also, unhandledRejection.

[jamestalmage]

Copying a my suggestion here:

Instead of separate errors and tests arrays, should it just be tests? A test could have a status attached (passed / failed), and all assertions with their respective results. Might be better than just standardizing errors
-- @jamestalmage

and a valid counterpoint:

we also need to store rejections and exceptions, which are not attached to any test and don't have test title, etc. So storing rejections and exceptions in tests doesn't sound right.
-- @vdemedes

[sotojuan]

What's the status of this?

[novemberborn]

@sotojuan it's up for the taking. Maybe we need to bikeshed the standardization details, though we could do that in a PR as well if you have a good idea on where to start.