Blueprint changed by Antonio Rosales: Whiteboard changed: Discussion: *Bug submission on charm failure. *Define a process around how charm maintainers respond to test failures and subsequent bugs. Can a user run a manual test and submit the test back to the bug report to update testing status to green. *Enable Autocharm tester to be more resilient against provider failures, and Jenkins usage. simulate provider failure, and be able to recover: $ juju ssh <MACHINE> sudo shutdown now * Define work items to execute auto charm testing on Go. - * Continuous Integration (also will help with gating on charm commits) + * Continuous Integration (also will help with gating on charm commits) + + Reference Links: + *Charm Test Spec [html] https://juju.ubuntu.com/docs/charm-tests.html + * Charm Test Speck [source] http://bazaar.launchpad.net/~juju/juju/docs/view/head:/source/charm-tests.rst + * CharmTester Charm http://jujucharms.com/~mark-mims/oneiric/charmtester + * Jenkins Charm Testing: https://jenkins.qa.ubuntu.com/view/Charms/
-- Juju Charm Testing https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
