npm / npm-audit-report / 83

100%

master: 100%

push

travis-ci

fix(tests): a test should not cause side-effects in other tests (#23)

If a fixture object was modified in one test, the modification would be visible
to other tests using the same fixture object.

I encountered this problem whilst testing an upcoming PR. This change makes
every usage of a fixture a new object. I'm open to suggestions on alternative
solutions, such as specifying that fixture modification is a test failure.

97 of 97 branches covered (100.0%)

Branch coverage included in aggregate %.

205 of 205 relevant lines covered (100.0%)

54.75 hits per line