PragTob / benchee / 617

94%

master: 94%

push

travis-ci

after_scenario with inputs implementation

Pondered whether after_scenario should behave like before_* i.e.
the input can be altered and passed on. Didn't see much sense
in that though as the last value (global_after_scenario) will go
nowher and the values aren't passed to any benchmarking function.

Also for consistency with `after_each` I decided to just pass them
the output of the last before_scenario (just like all after_each's
just get the return value of the benchmarking function).

2 of 2 new or added lines in 1 file covered. (100.0%)

338 of 358 relevant lines covered (94.41%)

33845.22 hits per line