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

Test summary accessible inside the teardown function #647

Closed
zypherman opened this issue May 23, 2018 · 3 comments · Fixed by #1768
Closed

Test summary accessible inside the teardown function #647

zypherman opened this issue May 23, 2018 · 3 comments · Fixed by #1768
Assignees
Milestone

Comments

@zypherman
Copy link

It would be really helpful to allow access to the entire test summary inside the teardown function. There is a lot of helpful information that is inside the summary that is written to the console after the test shuts down. If you could grab onto that inside the teardown function it would make reporting a lot easier.

@na--
Copy link
Member

na-- commented May 24, 2018

I agree, this would be helpful in some use cases, but like I mentioned in the slack chat about it, I'm not sure how easy it would be to implement with the cloud/cluster execution. Most of the summary stats (basically any Trends, where we calculate things like p(90)) are not easily merge-able in a distributed execution scenario, so we probably have to haul a lot of raw data between nodes.

@na--
Copy link
Member

na-- commented May 29, 2018

Related issues: #351 and #355

@na--
Copy link
Member

na-- commented Jan 13, 2021

To tie things up here, this is now closed by #1768. As you can see from the PR, the summary is not accessible from inside of teardown(), mostly because teardown() can produce metrics that affect the summary, and because teardown() works in the cloud and this new feature isn't yet supported there. So, instead, this can be achieved by exporting a function called handleSummary().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants