DavidCain / mitoc-member / 34 / 1

95%

master: 95%

push

travis-ci

Use mock.patch.object where sensible

Rather than worrying about the exact import path we're mocking, I often
prefer to just mock directly from an object. I think this is more
readable, and also ensures that we're properly mocking the actual
object.

64 of 86 branches covered (74.42%)

Branch coverage included in aggregate %.

492 of 566 relevant lines covered (86.93%)

0.87 hits per line