Commit Graph
6 Commits
Author SHA1 Message Date
Jason Peacock 3aa26a3e27 Moved types::Second and types::Unit to new unit module
Also review feedback.
2018-11-04 10:15:05 +01:00
Jason Peacock f0b6f130ea Add option to set time units for CLI & Markdown, closes #80
Add option to set the time units to either `MilliSecond` or `Second`
for both CLI output and Markdown export, overriding the default logic.
2018-11-04 10:15:05 +01:00
Jason Peacock 01581f60e0 Add option to set the shell, closes #61
Allow the user to set the shell used for executing benchmark commands.

The option (-S/--shell) can be overridden, when there are duplicate
options the last option's value will be used.
2018-10-31 18:02:37 +01:00
Jason Peacock 0b18446c0c Addressed review feedback 2018-10-28 08:46:01 +01:00
Jason Peacock 29804c54c9 Change markdown export to use seconds, closes #71
The markdown results exporter was using milliseconds, but the other
results exporters are using the default seconds unit.

Apply some refactoring so the same logic used to select units for the
CLI output can be used to select the units for the markdown exporter.

Now the units of the markdown exporter match that of the CLI.

When there are multiple benchmarks, the CLI will choose the
appropriate unit for each benchmark separately. In this case, the
markdown exporter will use the first benchmark to select the units for
all the results.

*This will change the markdown results for all users from milliseconds
to seconds, a UX breaking change.*

Add unit tests for the markdown exporter to verify the output.

Issue #80 proposes a new option to choose the units used for both the
CLI report and results export.
2018-10-28 08:46:01 +01:00
Jason Peacock 3246ec27e1 Compact output, add -s color option, closes #70
Strip the empty lines within the results for each benchmark, but keep
the empty line between each benchmark, and before the summary.

Add `color` style option to show color but not be interactive (no
progress bar).
2018-09-28 21:57:53 +02:00