Add json summary output for k6 scenarios #19

Merged
abereziny merged 1 commit from feature-add-json-output into master 2023-03-01 12:12:23 +00:00
abereziny commented 2023-03-01 08:32:35 +00:00 (Migrated from github.com)

Add json summary output for k6 scenarios preserving also stdout output.

The reasons for this change is to provide ability to tests to have the output json and parse it for test cases purposes.
We also leaving the stdout output for easy human readability.

Add json summary output for k6 scenarios preserving also stdout output. The reasons for this change is to provide ability to tests to have the output json and parse it for test cases purposes. We also leaving the stdout output for easy human readability.
anikeev-yadro (Migrated from github.com) reviewed 2023-03-01 08:32:35 +00:00
jingerbread (Migrated from github.com) reviewed 2023-03-01 08:32:35 +00:00
fyrchik commented 2023-03-01 10:30:07 +00:00 (Migrated from github.com)

Could you describe the reasons for this change a bit here or in the commit message?

Could you describe the reasons for this change a bit here or in the commit message?
fyrchik commented 2023-03-01 10:40:54 +00:00 (Migrated from github.com)

Also, there is ./k6 run --log-format json or does it do something different?

Also, there is `./k6 run --log-format json` or does it do something different?
abereziny commented 2023-03-01 11:18:15 +00:00 (Migrated from github.com)

Also, there is ./k6 run --log-format json or does it do something different?

We don't want time-stamped data-points, just the aggregated summary.

> Also, there is `./k6 run --log-format json` or does it do something different? We don't want time-stamped data-points, just the aggregated summary.
abereziny commented 2023-03-01 11:22:08 +00:00 (Migrated from github.com)

Could you describe the reasons for this change a bit here or in the commit message?

This is the from the docs:
https://k6.io/docs/results-output/end-of-test/custom-summary/#use-handlesummary

We want:

  1. Both outputs (default stdout + json)
  2. Json should be end-of-test summary, not log or data-points
> Could you describe the reasons for this change a bit here or in the commit message? This is the from the docs: https://k6.io/docs/results-output/end-of-test/custom-summary/#use-handlesummary We want: 1. Both outputs (default stdout + json) 2. Json should be end-of-test summary, not log or data-points
fyrchik (Migrated from github.com) approved these changes 2023-03-01 11:53:27 +00:00
dansingjulia (Migrated from github.com) approved these changes 2023-03-01 11:58:10 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/xk6-frostfs#19
No description provided.