Uniter tests for update-status hook - BLOCKER
Nate Finch
nate.finch at canonical.com
Mon Jul 20 20:31:59 UTC 2015
On Mon, Jul 20, 2015 at 3:05 PM roger peppe <roger.peppe at canonical.com>
wrote:
> On 20 July 2015 at 19:41, Nate Finch <nate.finch at canonical.com> wrote:
> > You should be able to get to 80% code coverage (and near 100% logic
> coverage)
> > without using anything outside your package.
>
> Shouldn't those numbers be the other way around? I don't see how
> you could possibly get to ~100% of logic coverage if only 80%
> of the code is covered.
>
Yes, you're right, any runnable code is logic. But there's often some
uninteresting glue code that is not really the meat of the logic, that may
be hard to test and unlikely to break. I guess that's really too vague as
a guideline, though. My point is - you should be able to test most of your
code without having to spin up a server - even a fake test server.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20150720/0743b899/attachment-0001.html>
More information about the Juju-dev
mailing list