Re-analyzing results use case.

[hborham]

This is a very useful extension. I love the simplicity, ease and ui.

I'd be curious if there's a way to re-analyze results. For example, using the output json of k6 and loading them into your dashboard. This would allow for re-investigating results from an old execution run output.

[szkiba]

Thank you for feedback and suggestion.
Some major improvements to the dashboard are expected in the near future (downloading data from the start of the test, creating reports, etc.). The ability to analyze afterwards is useful for this, thank you.

[kempsterc]

#22

[kempsterc]

If you have an idea of what needs to be done, or changed. I can create a Pr

[szkiba]

Hi guys, this feature is on the way, as I promised earlier to @hborham so @kempsterc don't waste time on it :) Tomorrow I'm going to publish a new release which will include it.

[kempsterc]

That's awesome! Happy to review

Love this extension

[szkiba]

Sorry to say, but I need a few days to publish a new release. It seem working but I'd like to refactor a bit before release :)

[szkiba]

Hi @hborham, @kempsterc ,

The new release is ready:
https://github.com/szkiba/xk6-dashboard/releases/tag/v0.4.3

main new features:

• replay results: the extension adds a dashboard replay subcommand to the k6 command line, which can be used to play back test run results previously saved in JSON format for the dashboard.

$ ./k6 dashboard replay --help

The replay command load the saved JSON results and replay it for the dashboard UI.
The compressed file will be automatically decompressed if the file extension is .gz

Usage:
  k6 dashboard replay file [flags]

Flags:
      --config string   UI configuration file location (default: '.dashboard.js')
      --host string     Hostname or IP address for HTTP endpoint (default: '', empty, listen on all interfaces)
      --open            Open browser window automatically
      --period 10s      Event emitting frequency (default: 10s), example: `1m` (default 10s)
      --port int        TCP port for HTTP endpoint (default: 5665), example: 8080 (default 5665)
  -h, --help            help for replay

[kempsterc]

Amazing! About to try it out! Thank you

[hborham]

Just tried, this is amazing! It works exactly how I was hoping! Thank you for adding this feature so quickly!