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
Sending summary to remote endpoint #3683
Labels
Comments
hi, any update here ? |
any update here ? |
Hey @ameetpal,
in alternative to the other already proposed options, this is one of the reasons why Grafana Cloud k6 exists, did you give it a try? |
yes, those options will not work for us |
Closing because the related pull request has been merged and the new event will be available in k6 v0.51.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
Hey,
Our team is providing k6 testing as a platform in our org and other teams use our platform to test their services. To collect the test result summary, we are exposing an endpoint and in test scripts we have to overide the handleSummery function and write the code to send it to a server. As indicated in K6 docs
https://k6.io/docs/results-output/end-of-test/custom-summary/#example-send-data-to-remote-server
However, every test script have to export handleSummary function, So we were looking into the solution were we can provide a default behaviour for sending the summary data.
We have already raised this issue in Grafana community and we were suggested to listen to Event in custom K6 extension, so we are currently working making a new extension for this and will be release this for public use also.
https://community.grafana.com/t/exploring-direct-event-consumption-in-k6-seeking-alternatives-to-handlesummary-override/116038
However, after looking into the code, we found out that there is no event with summary data
Suggested Solution (optional)
So to get summary data in event we have created a new event TestSummaryGenerated, which our extension will listen to. I have already raised a PR for this, please review it and let me know if any additional change is required
PR:- #3682
Already existing or connected issues / PRs (optional)
#3682
The text was updated successfully, but these errors were encountered: