José,
That's a good point that we definitely need recommended best practices
for writing charm tests. I am also behind using the built-in
unittest[1] library to organize and structure the tests. I am also
behind encouraging combining tests inside test cases where possible,
with the caveat that
On Tue, Apr 14, 2015 at 6:09 AM, Robert Day robert@metaswitch.com
wrote:
Thanks for the response! I’ve:
* found https://code.launchpad.net/~whitmo/juju-deployer/git-clone-fix
and applied those changes to my local copy of juju-deployer
* removed the “--depth 1” from vcs.py
* corrected my
Thanks for the response! I’ve:
* found https://code.launchpad.net/~whitmo/juju-deployer/git-clone-fix and
applied those changes to my local copy of juju-deployer
* removed the “--depth 1” from vcs.py
* corrected my bundle to the below
services:
clearwater-bono:
charm: clearwater-bono
I'd like to hear, what are other problems or common things people
encounter when writing tests?
On 04/14/2015 11:07 AM, Cory Johns wrote:
As Nate pointed out, I forgot the link. _
[1]: https://docs.python.org/2/library/unittest.html
On Tue, Apr 14, 2015 at 1:59 PM, Cory Johns
This is a bit rough, I have not had time to make it better or add the other
less common use cases or HA but should give a more decent explanation
https://docs.google.com/a/canonical.com/document/d/1AtAo-uxED5TvXahJNytF-PIswRv9T0lewcyu699Rpyk/edit?usp=sharing
On Wed, Mar 25, 2015 at 3:44 PM, Eric
