lp:~tvansteenburgh/charmtester/bundletester

Branch merges

Propose for merging

No branches dependent on this one.

Ready for review for merging into lp:~bcsaller/charmtester/bundletester

Benjamin Saller: Pending requested 2014-07-17

Diff: 157 lines (+32/-26)

7 files modified

bundletester/builder.py (+1/-1)
bundletester/config.py (+3/-3)
bundletester/runner.py (+6/-3)
bundletester/spec.py (+15/-13)
bundletester/tester.py (+2/-1)
tests/test_config.py (+4/-4)
tests/test_spec.py (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

50. By Tim Van Steenburgh on 2014-09-07

Change default test search pattern

- Find all executable tests in the tests/ dir by default,
  instead of just those that begin with a number
- cd to the testdir when running tests in order to play
  nicely with amulet's charm lookup machinery
- Fix failing tests caused by new defaults

49. By Tim Van Steenburgh on 2014-08-18

Use --force when destroying env

48. By Tim Van Steenburgh on 2014-08-14

Unique exit code to signify 'No tests found'

Also make exit msg more accurate - 'No tests found' does not necessarily
imply that test target was not a bundle or charm.

47. By Tim Van Steenburgh on 2014-08-11

More accurate bundle detection

Make sure 'services' key is not actually a Charm config option

46. By Tim Van Steenburgh on 2014-07-17

Run successfully even if no .bzr dir

45. By Tim Van Steenburgh on 2014-07-16

Change config default values

44. By Benjamin Saller on 2014-06-05

resolve setup/teardown in testdir, not same dir as exec

43. By Benjamin Saller on 2014-06-04

added --no-destroy option, better charm inference regex

42. By Benjamin Saller on 2014-06-03

track when we did bootstrap vs connect and enable destroy-env

41. By Benjamin Saller on 2014-06-03

Better control over when deploys happen (only for bundles, not charms or testdirs (though testsdirs might be an option))

Better control over excluding suites

Fixed bootstrapping controls

More consistent suite management (and improved modeling wrt to test ownership)

BundleWatcher has a model to extract full (not lightweight) versions of the charms with --devel