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

Report an error #2

Open
thiagodp opened this issue Jul 26, 2018 · 1 comment
Open

Report an error #2

thiagodp opened this issue Jul 26, 2018 · 1 comment

Comments

@thiagodp
Copy link

Fail and error may need to be reported differently. A fail usually occurs when an assertion is incorrect; an error occurs because of an exception is thrown and it is not catch, or because of a problem with the source code that will be only detected at run-time.

ZAP could represent the event error. This event would probably happen only when kind is test.

@jamiebuilds
Copy link
Member

Hmm... I do want to limit the number of possible completion events to two so that its always binary "these tests results should be considered as passed/failed"

I wouldn't be opposed to providing different reasons for negative cases though.

There could be other events that fire, there could be another field "reason" which is a enum of possible failure types. But whatever it is should be ignorable if all you care about is a yes or no answer to if tests passed

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