You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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().
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.
The text was updated successfully, but these errors were encountered: