Blueprint changed by Clint Byrum: Whiteboard set to: - to jenkins or not to jenkins? Current documentation on Charm testing: https://juju.ubuntu.com/docs/charm-tests.html CI: go team has unit/hybrid tests (David Cheney) Goals: user experience testing on trunk full set of functional tests (also have "live tests" core against the real provider) five charms to test against create dedicated test charms how do we integrate providers? Work Items: charmtester on go asap juju-functionality test charms -Charm on how to fully exercise Juju capabilities - repeatedly open-port/closes-port etc, or relation setting exercising with continuous handshaking document repeating these tests publicize embedded charm tests test charms on demand for review (in addition to jitsu test from local env) juju test docs move out of draft status testrunner needs to be resilient against fixture failure -Have auto charm tester first check the health of the provider before doing follow on charm testing. charmtester: mail juju-dev on break add unit tests as gate maintainer and/or file bug
-- Juju CI (Go and Python) https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-ci -- 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
