introduce --iterations config option (which auto-enables --no-reset-metrics as otherwise the final metrics can be very confusing/irrelevant; when using --iterations the metrics should confirm that all Scenarios and Transactions were run as intended)
track iterations in GooseUser
exit cleanly if iterations is set and GooseUser executes the scenario this many times
o this required adding a new channel where GooseUsers can report to the Parent they are shutting down
introduce scenario metrics, disabled with --no-scenario-metrics (or GooseDefault::NoScenarioMetrics)
o this was required to provide visibility into how the load test is configured, ie when --iterations 1 is specified
introduce scenario log, enabled with --scenario-log FILE-NAME (or GooseDefault::ScenarioLog) and formatted with --scenario--format FORMAT (or GooseDefault::ScenarioFormat)
o all metrics can be logged, so we add this log type too
add tests
o stand-alone and gaggle tests, with different schedulers
o found/fixed a few gaggle bugs introduced when adding TestPlan support
update documentation
o added new page for Scenario Logs
o updated the Metrics page so example includes Scenario Metrics
o general cleanups/updates to cross-reference Scenarios (and Transactions, and Requests)
o started switching from .png images to .jpg images in the book for better compression, due to the limit of Cargo package sizes on crates.io
--iterations
config option (which auto-enables--no-reset-metrics
as otherwise the final metrics can be very confusing/irrelevant; when using--iterations
the metrics should confirm that all Scenarios and Transactions were run as intended)--no-scenario-metrics
(orGooseDefault::NoScenarioMetrics
) o this was required to provide visibility into how the load test is configured, ie when--iterations 1
is specified--scenario-log FILE-NAME
(orGooseDefault::ScenarioLog
) and formatted with--scenario--format FORMAT
(orGooseDefault::ScenarioFormat
) o all metrics can be logged, so we add this log type too.png
images to.jpg
images in the book for better compression, due to the limit of Cargo package sizes on crates.ioA new SCENARIO METRICS table makes it clear that
--iterations
was used (in this case--iterations 2
):This new table also includes a graph in the
--report-file
: