cf-charmers team mailing list archive

[Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>]

Hook tests will typically be integration tests. When those call methods
that are specific to the charm though those methods should be unit tested.


On Thu, Apr 10, 2014 at 10:01 AM, <prismakov@xxxxxxxxx> wrote:

> Hi Ben, thank you for your answer,
>
> To be more specific, do we need test for decorated hook functions like
> install, start, nats-relation-changed etc?
>
> -A
>
> On Apr 10, 2014, at 18:20, Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>
> wrote:
>
> We want two levels of tests in charms
>
> 1. Unit tests, just like we added to charm helpers. At minimum these
> should exercise any new methods introduced by the charm such that we are
> confident that the code works.
>
> 2. Amulet integration tests, for charms these should connect the minimum
> number of components (other charms) and prove that they integrate properly.
>
> 3. And what I'm still working on are bundle level tests where we deploy
> the whole bundle and run tests on that. CATs in the main thing here.
>
> Our bundle test plan includes pulling down all the charms in the bundle,
> running all its unit tests, then its integration, then if all those pass
> the bundle level test which are expensive.
>
> Thanks,
> Ben
>
>
> On Thu, Apr 10, 2014 at 7:02 AM, <prismakov@xxxxxxxxx> wrote:
>
>> He guys,
>>
>> Do we need cover with unit tests our charm's hooks? If so is there any
>> example in existing charms?
>>
>> -Alex Prismakov
>> --
>> Mailing list: https://launchpad.net/~cf-charmers
>> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~cf-charmers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>