Add json summary output for k6 scenarios #19
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#19
Loading…
Reference in a new issue
No description provided.
Delete branch "feature-add-json-output"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Could you describe the reasons for this change a bit here or in the commit message?
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.
This is the from the docs:
https://k6.io/docs/results-output/end-of-test/custom-summary/#use-handlesummary
We want: