Modularization of Testdrive
As part as the Testdrive Front-end GSoC project, Testdrive needs to be modularized to be able to have a back-end and different front-ends
Blueprint information
- Status:
- Complete
- Approver:
- Dustin Kirkland
- Priority:
- Undefined
- Drafter:
- Andres Rodriguez
- Direction:
- Needs approval
- Assignee:
- Andres Rodriguez
- Definition:
- Approved
- Series goal:
- Proposed for maverick
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Dustin Kirkland
- Completed by
- Dustin Kirkland
Related branches
Related bugs
| Bug #553616: Improve method to obtain current development release for ISO list generation | Fix Released |
Sprints
Whiteboard
kirkland -- I agree with Andres' intentions to modularize and object-orient testdrive. I think this should be mostly in place by UDS-Maverick, so I don't think a UDS session would be necessary on this point. Andres should ask for a peer code review by some Ubuntu python experts (perhaps by emailing ubuntu-devel@).
Work items for testdrive-
[andreserl] Current Code examination: DONE
[andreserl] Separation of reusable code with interface only code: DONE
[andreserl] Design of Testdrive Module Class: DONE
[andreserl] Implementation of Testdrive Module Class: DONE
[andreserl] Testing: DONE
[andreserl] Request python-OO code review and implement feedback: TODO
[kirkland] Merge upstream: DONE
[kirkland] Release working OO testdrive to Maverick Alpha1: DONE
NOTES:
Related blueprint: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
