Faster Development Cycle for Tested Charms

Registered by Gary Poster

[GOAL]
Make charm tests faster to run
Make charm tests faster to develop
Make charm tests more robust
[RATIONALE]
We have very few charms with automated tests. Developing charm tests is slow because running them is slow, especially in repetition, while you are developing. Test results are also often flaky. What can we do to make this faster and more reliable, both in Juju core and in the ecosystem tools?

Blueprint information

Status:
Complete
Approver:
Antonio Rosales
Priority:
Undefined
Drafter:
Gary Poster
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Antonio Rosales

Related branches

Sprints

Whiteboard

[arosales: 2013-05-02] Moved to https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing. This Blueprint is deprecated.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.