Automated testing of packages

Registered by Ian Jackson on 2005-10-25

Ways to automatically check certain package properties which we regard as essential. Currently it is possible to upload packages which do not work at all, can disrupt the packaging system, are uninstallable, or have a broken build system. We want to introduce a set of universally applicable tests that reject such packages before they irritate anyone. To the extent possible, a package should also be able to check its own functionality to make regressions immediately visible.

Blueprint information

Status:
Complete
Approver:
Colin Watson
Priority:
High
Drafter:
Ian Jackson
Direction:
Needs approval
Assignee:
Ian Jackson
Definition:
Approved
Series goal:
Accepted for dapper
Implementation:
Implemented
Milestone target:
None
Started by
Ian Jackson on 2006-08-16
Completed by
Ian Jackson on 2006-08-16

Related branches

Sprints

Whiteboard

The basic framework as specified in AutomatedTesting is complete. Further work is required to provide automatic testing during builds. Extending the range of tests is also required - an indefinite task.
Set to Implemented 25 Feb 2006. JMW

(?)

Work Items