1250
94%
master: 94%

Ran 09 Feb 2019 02:03PM UTC

Jobs 2

Files 38

Run time 2min

Badge

Embed ▾

pending completion

Build # 1250

Build Type

push

travis-ci

Committed by

PragTob

Commit Message

Add Scenario.data_processed? to simplify checks in formatters

Formatters often have to check whether run time or memory data
was processed - so if data was collected at all and if statistics
have already been generated so that they can be rendered.

This should simplify this/not tie all of them to the internal
data structure.

The decision as made to check directly on statistics to see if
values actually made it into it, rather than just checking the
configuration if it was intended to measure, so that we're sure
that values are there.

This might sound like a check on `Suite` to check if all scenarios
have all data might be a good thing, however mostly formatters
split things by input so it will more often be checked on a
sub set of scenarios or individual scenarios.

This PR doesn't use the function in our formatters yet, to avoid
merge conflicts with #264 :) #264 will have to adjust its
implementation though, but that should be very easy and straight
forward.

Run Details

588 of 627 relevant lines covered (93.78%)

3798.66 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
5	1250.5	09 Feb 2019 02:03PM UTC	0	93.78	Travis Job 1250.5
6	1250.6	09 Feb 2019 02:05PM UTC	0	93.78	Travis Job 1250.6

Source Files on build 1250

Detailed source file information is not available for this build.

PragTob / benchee / 1250
94%
master: 94%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1250

PragTob / benchee / 1250 94% master: 94%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1250

PragTob / benchee / 1250
94%
master: 94%

README BADGES
x