I published a couple of new Python packages aimed at making unit tests for
charms easier and nicer:
They implement the classic approach  of replacing the "boundaries" of a
charm (hook tools, processes, filesystem, network, etc) with realistic
fakes, so your unit tests run actual code as much as possible and you don't
have to mock internal APIs that directly or indirectly interact with the
boundaries (often leading to mocking explosion).
Besides the package documentation, you might want to have a look to the
jenkins charm reactive rewrite branch  to see some real-world use.
If there's interest around this, we could move the code under the juju
GitHub tree, or even merge it to the charm.unit package .
Juju-dev mailing list
Modify settings or unsubscribe at: