Hi Roman, all, You might also find charmbox [1] useful. With charmbox you have your testing environment in a container so you do not "pollute" your work space with whatever the tests want to install in your system.
The bigtop charms have an action called smoke-test that is meant to perform a quick sanity check. The smoke-test action may run the bigtop smoke tests for the deployed roles given that the bigtop smoke tests exist and their time requirements are reasonable. We also have a test in every charm that deploys an infrastructure and then triggers the smoke-test action. Note that since we have charms under review you might need to alter the above test so as to deploy charms that already exist. For example, while testing Kafka you might need to deploy apache-zookeeper in the place of (bigtop) zookeeper in [2]. Thanks, Konstantinos [1] https://github.com/juju-solutions/charmbox [2] https://github.com/juju-solutions/bigtop/blob/kafka/bigtop-packages/src/charm/kafka/layer-kafka/tests/02-smoke-test.py On Tue, Jun 28, 2016 at 3:07 AM, Konstantin Boudnik <[email protected]> wrote: > Last time I checked (back in April) bundletester wasn't working with Juju > 2. > Has it been fixed recently? > > Cos > > On Mon, Jun 27, 2016 at 04:49PM, Merlijn Sebrechts wrote: > > Hi Roman > > > > > > I personally use bundletester to run the tests. You can point > bundletester > > to a single charm instead of a bundle: > > > > bundletester -t ~/charms/trusty/mycharm -l DEBUG > > > > > > More info on its github page: > https://github.com/juju-solutions/bundletester > > > > > > > > Kind regards > > Merlijn > > > > 2016-06-27 16:22 GMT-07:00 Roman Shaposhnik <[email protected]>: > > > > > Antonio, Pete, > > > > > > thanks a million for your feedback so far. Super helpful! One last > > > question I've > > > got before I can start reviewing your Charms contributions is how to > > > trigger > > > tests that come in every charm under tests? Reading Juju Developer docs > > > seems to be talking about some kind of a test runner, but I can't quite > > > figure > > > out where to get it and how to point it at just a single charm I'd > like to > > > test. > > > > > > Any suggestions? > > > > > > Thanks, > > > Roman. > > > > > > On Thu, Jun 23, 2016 at 10:29 AM, Antonio Rosales > > > <[email protected]> wrote: > > > > On Thu, Jun 23, 2016 at 7:18 AM, Konstantin Boudnik <[email protected]> > > > wrote: > > > >> Oh may be, just may be, be a man and flush the damn thing with > Ubuntu :) > > > > lol :-) > > > > > > > > A couple of options for OSX: > > > > Run the client native and point at a public cloud: > > > > https://jujucharms.com/docs/stable/getting-started#mac-osx > > > > Run in LXC containers locally via the Vagrant Juju box (as Pete > pointed > > > out): > > > > - https://jujucharms.com/docs/stable/config-vagrant > > > > - https://jujucharms.com/docs/stable/howto-vagrant-workflow > > > > Run in Docker, works best to point at a public cloud, but there are > > > > work arounds to connect to an existing LXC enviornment > > > > - https://github.com/juju-solutions/charmbox (dev test wtih charms) > > > > - https://github.com/juju-solutions/jujubox (using juju to mainly > > > > deploy charms) > > > > > > > > If you don't have access to a public cloud there is a Juju Charm > > > > Developer program we encourage folks to apply for if they are going > to > > > > be actively teting and/or developer charms. Canonical will pay for > > > > your AWS run time for Charm development per: > > > > https://developer.juju.solutions/ > > > > > > > > General getting started instructions: > > > > https://jujucharms.com/get-started > > > > > > > > If you have any questions or run into issue please feel free to give > > > > me a ping in IRC (arosales) in #bigtop or #juju on Freenode. > > > > > > > > We are actively developing 2.0 version of Juju and there are still > > > > some bugs in there, 1.25 is the stable. I prefer Juju 2.0. Juju 2.0 > > > > instructions are in the devel section of our docs: > > > > https://jujucharms.com/docs/devel/getting-started There is also a > > > > bug[0] in Xenial for Vagrant images so no Xenial vagrant images yet. > > > > > > > > [0] https://bugs.launchpad.net/cloud-images/+bug/1565985 > > > > > > > > -thanks, > > > > Antonio > > > > > > > >> > > > >> On Thu, Jun 23, 2016 at 02:42AM, Pete Vander Giessen wrote: > > > >>> Hi Roman, > > > >>> > > > >>> I believe that you can use vagrant to test Juju on an OSX box, > with a > > > local > > > >>> lxd provider. Docs here: > > > https://jujucharms.com/docs/1.25/config-vagrant > > > >>> > > > >>> I haven't tried it myself, though, so I don't know whether there > are > > > any > > > >>> gotchas. @Kevin: is vagrant the way to go, or are there better > ways to > > > do > > > >>> things on OSX? > > > >>> > > > >>> ~ PeteVG > > > >>> On Wed, Jun 22, 2016 at 3:41 PM Roman Shaposhnik < > [email protected] > > > > > > > >>> wrote: > > > >>> > > > >>> > Hi! > > > >>> > > > > >>> > I see a lot of JIRAs coming in with Charm support. This is super > > > >>> > exciting for me and I'm more than happy to review and commit. > > > >>> > > > > >>> > However, given the # of them coming, I'm wondering if somebody > > > >>> > can comment on a way to test these without spinning full blown > > > >>> > Juju deployments on EC2. > > > >>> > > > > >>> > So... does somebody on a Mac OS (yes I know -- its a corporate > > > decision > > > >>> > :-() > > > >>> > test something like (see my last comment there): > > > >>> > https://issues.apache.org/jira/browse/BIGTOP-2482 > > > >>> > > > > >>> > Thanks, > > > >>> > Roman. > > > >>> > > > > > > > > > > > > > > > > > -- > > > > Antonio Rosales > > > > Ecosystem Engineering > > > > Canonical > > > >
