365
100%
master: 100%

Ran 07 May 2019 10:42AM UTC

Jobs 4

Files 32

Run time 2min

Badge

Embed ▾

pending completion

Build # 365

Build Type

push

travis-ci

Committed by

Sinjo

Commit Message

Make it clear when error comes from mocking in tests

This is a small quality of life enhancement when debugging test
failures. When you comment out the catch-all `rescue` in the production
code of Prometheus::Middleware::Collector, you see a `NoMethodError`
with no stack or message attached.

Initially, this is pretty confusing, and you may think it was the reason
for your tests failing! In fact, it's to test the catch-all rescue.

This commit makes it really explicit that the error is deliberately
coming from the tests.

Signed-off-by: Chris Sinjakli <chris@gocardless.com>

Run Details

1380 of 1380 relevant lines covered (100.0%)

41.92 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	365.1 (2.3.8)	07 May 2019 10:42AM UTC	100.0	Travis Job 365.1
2	365.2 (2.4.5)	07 May 2019 10:42AM UTC	100.0	Travis Job 365.2
3	365.3 (2.5.3)	07 May 2019 10:42AM UTC	100.0	Travis Job 365.3
5	365.5 (jruby-9.1.5.0)	07 May 2019 10:45AM UTC	0.0	Travis Job 365.5

Source Files on build 365

Detailed source file information is not available for this build.

prometheus / client_ruby / 365
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 365

prometheus / client_ruby / 365 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 365

prometheus / client_ruby / 365
100%
master: 100%

README BADGES
x