Ran
|
Jobs
4
|
Files
13
|
Run time
3min
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/nock/nock/commit/<a class=hub.com/nock/nock/commit/5c67b46ed2ed74abed05430eb3991332c35dd241">5c67b46ed<a href="https://github.com/nock/nock/commit/5c67b46ed2ed74abed05430eb3991332c35dd241">">test(test_aws_dynamo): Remove AWS Dynamo functional test This reverts </a><a class="double-link" href="https://github.com/nock/nock/commit/<a class="double-link" href="https://github.com/nock/nock/commit/90662fc1fcc74586b157dddd5a408a692579ff20">90662fc1f</a>">90662fc1f</a><a href="https://github.com/nock/nock/commit/5c67b46ed2ed74abed05430eb3991332c35dd241"> which added a wide-bracket functional test for #223. I appreciate the goal of defensively avoiding a regression. I could imagine circumstances where it’s worth installing some prominent client library to ensure nock keeps working with some complex workflow. However the default when finding a bug in nock should be to isolate the bug in a small test case, and continue to maintain that small example to protect from regressions. In this case there wasn’t even a bug. There’s another regression test for #256 which also uses `aws-sdk` but that’s going to take a bit more effort to rework.
766 of 895 branches covered (85.59%)
Branch coverage included in aggregate %.
1418 of 1521 relevant lines covered (93.23%)
75088.15 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
2 | 2470.2 | 13 |
89.98 |
Travis Job 2470.2 | |
3 | 2470.3 | 13 |
90.07 |
Travis Job 2470.3 | |
4 | 2470.4 | 13 |
89.53 |
Travis Job 2470.4 | |
6 | 2470.6 (coverage) | 13 |
89.98 |
Travis Job 2470.6 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|