Blueprint changed by Marco Ceppi:
Work items changed:
Work items:
[marcoceppi] Integration Testing includes framework that charm authors can
write tests against (embedded in the charm) (amulet): INPROGRESS
[marcoceppi] Jenkins testing on new merge proposal, on success it is a
candidate
Blueprint changed by Marco Ceppi:
Work items changed:
Work items:
[marcoceppi] Integration Testing includes framework that charm authors can
write tests against (embedded in the charm) (amulet): INPROGRESS
- [marcoceppi] Jenkins testing on new merge proposal, on success it is a
candidate
Blueprint changed by Marco Ceppi:
Work items changed:
Work items:
- Integration Testing includes framework that charm authors can write tests
against (embedded in the charm): TODO
- Jenkins testing on new merge proposal, on success it is a candidate for
review: TODO
- Develop Juju test plugin
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Marco Ceppi:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Mark Mims:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing status
Blueprint changed by Antonio Rosales:
Work items set to:
Work items:
Integration Testing includes framework that charm authors can write tests
against (embedded in the charm): TODO
Jenkins testing on new merge proposal, on success it is a candidate for review:
TODO
Develop Juju test plugin (ie
Blueprint changed by Marco Ceppi:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Blueprint changed by Antonio Rosales:
Name: servercloud-r-juju-charm-testing = servercloud-s-juju-charm-testing
--
Juju Charm Testing
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charm-testing
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
13 matches
Mail list logo
