You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the test_number is attached to the Result object there's less work for an EventWatcher to do and it's more generically applicable.
Move the counter out of the TAP formatter and into the History object.
History will track the last test_number seen on a result, so others can check if an incoming result is out of order. History's accept_result will set the last number seen to the result's test_number OR increment it if it doesn't have one.
History will also track if it's seen any out of order results and hold onto a list of them.
The text was updated successfully, but these errors were encountered:
I don't think the History should do any implicit shenanigans about setting the counter to match the result test number. I'd rather that was explicit behavior than try to guess.
History doesn't currently track out of order tests, but I think that's a separate issue.
Now that the
test_number
is attached to the Result object there's less work for an EventWatcher to do and it's more generically applicable.Move the counter out of the TAP formatter and into the History object.
History will track the last test_number seen on a result, so others can check if an incoming result is out of order. History's accept_result will set the last number seen to the result's test_number OR increment it if it doesn't have one.
History will also track if it's seen any out of order results and hold onto a list of them.
The text was updated successfully, but these errors were encountered: