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

Adding timestamps to html or json report #2377

Closed
jonathan-boudreau-work opened this issue Jan 31, 2024 · 1 comment
Closed

Adding timestamps to html or json report #2377

jonathan-boudreau-work opened this issue Jan 31, 2024 · 1 comment

Comments

@jonathan-boudreau-work
Copy link

πŸ€” What's the problem you're trying to solve?

Making it easier to debug test failures.

✨ What's your proposed solution?

Add step timestamps to the html or json report.

⛏ Have you considered any alternatives or workarounds?

No.

πŸ“š Any additional context?

When running large test suites against environments it can be hard to troubleshoot due to the sheer number of logs generated. Having timestamps on the steps would make it easier to get a more appropriate range to filter logs on when using a logging tool like splunk.


This text was originally generated from a template, then edited by hand. You can modify the template here.

@davidjgoss
Copy link
Contributor

davidjgoss commented Jan 31, 2024

Thanks for raising @jonathan-boudreau-work. You mentioned both JSON and HTML so I'll address them separately:

JSON

The JSON formatter has durations for steps, but not timestamps. This format is in maintenance mode now and won't have any new functionality added. You can however use the message formatter which emits Cucumber Messages - these include testStepStarted events which have a timestamp.

HTML

What you're saying here chimes a lot with cucumber/html-formatter#283, where we want to change the design direction of the formatter to include more useful information for debugging, and this would definitely include timings.

@davidjgoss davidjgoss closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants