Blueprint changed by Antonio Rosales: Whiteboard changed: charm unit tests recap... we automatically run: - installation - graph test we'd like to additionally run - charm tests read the spec lp:juju in the "docs" dir... look for something like charmtests.rst http://bazaar.launchpad.net/~clint-fewbar/juju/charm-tests-spec/view/head:/source/charm-tests.rst policy stuff? tests required? just encouraged for now additional testing plugins possible: - nessus, etc against the running service - app-armor complain against running service - lint-type 'charm proof' - upgrade-charm tests - testing spread with add-unit - coverage ??? - watching relation settings?????? please put all projects in one of: charm-tools juju-jitsu charms juju environments - include all of them, including MAAS support MAAS, other distro needs enable manual kicks from ~charmers (charmbot, but we prob wanna do that through openid over the web) - parameterized jenkins tests, both official and against specific distro needs charmtester is a *charm* in the charm store - test my custom stack of services is readily doable (contributions are welcome as always) jenkins file bugs when charms fail (close them when they pass again?) try for "maintainer" notification through launchpad how do long-failing tests relate to "series" freeze??? coverage tools possible? check out next cycle load testing for individual charms? for example, siege all charms with http interface scale testing? weekly large runs? really a _juju_ test and less a _charm_ test + + --- + Please integrate the spec @ https://wiki.ubuntu.com/BlueprintSpec [a.rosales].
-- Juju Charm Unit Tests https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-unit-tests -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
