Hey all Juju developers, Of all the wonders of creating and manufacturing charm code, testing said code is not as glamorous, or is it?
Whenever you release your next version of your code, make sure to have it tested on every supported operating system release. Does this sound tedious or cumbersome to you? It does not have to be that way. There are numerous tools and even services freely available to automate testing your software. For this post I would like to highlight Travis CI as an example of one of these services. How to do it? Simple, add a .travis.yml to your repository and add your repository to the Travis CI service [1]. Travis CI is based on Ubuntu technology enabling us to further empower their services with the likes of LXC/LXD to serve our purposes of testing Juju charms on vagarious operating system releases. Have a look at this example code: https://github.com/marcoceppi/charm-mysql/blob/cefb77fafcd1ee36d4dc30c14d07aa857d5273a2/.travis.yml And this is an example of the output it could provide for your code: https://travis-ci.org/marcoceppi/charm-mysql/builds/218456769 [1]: https://docs.travis-ci.com/user/getting-started/ Keep on hacking and testing your code in the free world! -- Frode Nordahl Software Engineer Canonical Ltd.
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
