Right now, TB is using the formatter to ask about test events. This is really the job of history. History is gathering events but not providing any convenient information about them.
is the plan set?
are we in a stream?
how deep into the stream?
what's the current test count?
A glaring problem is TB1->last_test_seen necessary because the formatter will reset its counter at the end of a stream leaving the builder to do its own tracking. The history object should track that.
From: @schwern Date: Sunday Jan 09, 2011 at 11:04 GMT Orig: https://github.com/Test-More/test-more/issues/105
Right now, TB is using the formatter to ask about test events. This is really the job of history. History is gathering events but not providing any convenient information about them.
A glaring problem is TB1->last_test_seen necessary because the formatter will reset its counter at the end of a stream leaving the builder to do its own tracking. The history object should track that.