search

zaptst / zap

A streamable structured interface for real time reporting of developer tools.
MIT License
120 stars 1 forks source link

Report an error #2

Open thiagodp opened 6 years ago

thiagodp commented 6 years ago

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 commented 6 years ago

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