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.

Sign up for GitHub

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

Jump to bottom

Provide better insight into what a harness did #265

Open
camshaft opened this issue Jan 30, 2025 · 0 comments · May be fixed by #268
Open

Provide better insight into what a harness did #265

camshaft opened this issue Jan 30, 2025 · 0 comments · May be fixed by #268
Labels
[E] User Experience An UX enhancement for an existing feature. Including deprecation of an existing one.

Comments

@camshaft
Copy link
Owner

Trying to debug what a harness did can be tricky with the current implementation. Ideally a harness would report a summary of its findings by default. This would include:

  • How long it ran
  • How many inputs it ran on
  • How many rejected inputs it encountered
  • Why it exited
    • Due to time limit exceeded?
    • Due to max iterations?
@camshaft camshaft added the [E] User Experience An UX enhancement for an existing feature. Including deprecation of an existing one. label Jan 30, 2025
@camshaft camshaft linked a pull request Feb 1, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[E] User Experience An UX enhancement for an existing feature. Including deprecation of an existing one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: print test outcome on exit camshaft/bolero
1 participant
@camshaft