Amulet, tools to help with test writing

[Stuart Bishop]

On Wed, Jul 10, 2013 at 12:35 AM, Marco Ceppi <marco.ceppi at canonical.com> wrote:

> I want to announce that the first version of a collection of tools I've been
> working on, aptly named amulet (lp:amulet), is available for testing. While
> the first release is small, only including one core function, I hope to grow
> the library of tools over the coming weeks based on feedback from charmers
> writing tests. The goal of this project is to become "charm-helpers for
> testing", where charm-helpers are used during charm execution, these are
> used during testing to streamline and simplify test writing.

Thanks for working on this :)

> I hope to have weekly updates to the tool set, now available in
> ppa:juju/pkgs, the current command available is a port of the jitsu watch
> command which can be used as follows

I was looking forward to this, but it seems the approach is the same
as what I already have and suffers from the same problem. It waits
until services and relations are in a success state, but for tests we
need to wait until all the queued triggers have completed *and* that
the services and relations are in a success state. Services and
relations can be setup, but the service still be in a state of major
flux and non-functional until the hook storm has died down and the
service is in a stable state. I can't see anyway of knowing this from
the output of juju status as the list of queued hooks is not exposed,
and was hoping you were going to reach into the mongo database and
extract the needed information or some other magic I hadn't thought
of.

Can you think of any way around this, or does juju need to expose a
list of running and pending hooks?

-- 
Stuart Bishop <stuart.bishop at canonical.com>