-
Notifications
You must be signed in to change notification settings - Fork 10
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
add timeline visualisation for parallel runners #126
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. |
Do we have any screenshots that show what the timeline formatter did? |
Sure. The purpose of the timeline is to show which thread/worker executed a scenario. This is helpful when analyzing the performance of parallel execution. I put some 60-70 tests into a single file and ran it parallel with a random delay in one of the steps.
The thread name can be derived from the Relevant sources: |
Thanks @mpkorstanje, yeah we could totally do this with the messages now. |
We're in the process of removing tight coupling to Gherkin 5 from Cucumber-JVM. Its TimelineFormatter is tightly coupled to Gherkin 5, and should be removed.
Moreover, the very useful functionality in
TimelineFormatter
should be available to users of other Cucumber implementations that support parallelism (currently only Cucumber.js).We already have early stage support for rendering Cucumber in cucumber-react, which is wrapped as a standalone command-line tool in html-formatter. It would make sense to improve
cucumber-react
with the ability to render the same UI as the Cucumber-JVMTimelineFormatter
(using React).Also see cucumber/common#755
/cc @charlierudolph @boaty82 @mpkorstanje @vincent-psarga
The text was updated successfully, but these errors were encountered: