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

Enhance history to watch and provide information about events #105

Closed
schwern opened this issue Jan 9, 2011 · 1 comment
Closed

Enhance history to watch and provide information about events #105

schwern opened this issue Jan 9, 2011 · 1 comment

Comments

@schwern
Copy link
Contributor

schwern commented Jan 9, 2011

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.

@schwern
Copy link
Contributor Author

schwern commented Jan 26, 2011

This is taken care of by plan(), stream_depth() and results_count().

exodist added a commit that referenced this issue Jun 5, 2024
Handle an event without a trace object in Test2::Compare::Event
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant