Juju feedback from the Launchpad Yellow Squad

Benji York benji at benjiyork.com
Wed Feb 15 20:32:08 UTC 2012

On Wed, Feb 15, 2012 at 3:18 PM, Kapil Thangavelu
<kapil.thangavelu at canonical.com> wrote:
> Excerpts from Graham Binns's message of Wed Feb 15 13:30:51 -0500 2012:
>>  * In order to run tests, there's a test wrapper (as proposed by Clint,
>>    IIRC). There seems to be no reason that this wrapper's functionality
>>    shouldn't be included in the main juju executable; developers
>>    shouldn't have to jump through hoops just to be able to run their
>>    tests.
> The testing story and tooling is still evolving. Part of the purpose of the
> wrapper is to encode variablility into package origin, so the runner can run
> against its own selection of charms. its not clear why this would be beneficial
> to have as part of the juju command.

As you point out, it's about storing local config in a place such that
it won't pollute charm tests; since juju already has a place to store
local config (~/.juju), it'd be nice to store it there instead of in a
wrapper script.

I would think non-charm-developers would also like such a feature since
it would mean that they would have to specify less configuration on
command-lines when invoking juju commands.
Benji York

More information about the Juju mailing list