charmrunner - automated charm testing tools

Antonio Rosales antonio.rosales at
Fri Feb 17 21:57:10 UTC 2012

On 02/17/2012 01:43 PM, Robbie Williamson wrote:
> On 02/17/2012 10:24 AM, Kapil Thangavelu wrote:
>> Hi folks,
>> After the testing discussion last week, i put together a python package for 
>> generating automated test plans, running them, and recording the results. It 
>> works by constructing a graph of the charm's dependencies and then creating a 
>> plan consisting of charms and their versions, and the relations to instantiate 
>> between the deployed services them to satisfy dependencies. 
> <blink>
>> The package is built as a set of standalone tools that can accomplish various 
>> common practices when testing a charm (snapshot/restore environment, service 
>> watching, environment loading), with a front end script to drive the 
>> whole process. The front-end script is meant to be easy to drive from jenkins, 
>> by hand, or via a REST queue.
>> There's a readme overview of the tools and downloads available at.
>> i've been able to deploy everything i thrown at it (mediawiki, 
>> openstack/nova-compute, etc). Semantic deficiencies in relation metadata have 
>> tripped up the tool, and i doubt its perfect. I expect it will see some 
>> iteration as it expands beyond minimal dependency deployment to testing what a 
>> charm provides.
>> Code, bugs, etc.
> This is pure awesomeness...thanks Kapil!

+1  good stuff, and I hear you are already working with Mark Mims on
integrating this into this automated charm testing framework.

-Antonio Rosales

More information about the Juju mailing list