On 11/15/2013 07:28 AM, Martin Pitt wrote:
Luke Yelavich [2013-11-15 15:03 +1100]:
* Received a request from #ubuntu-devel to fix an important package
that was broken, due to empty debs other than docs. I wonder whether
auto pkg testing should check for this...
Indeed, that's why it's useful to have even the simplest "does my
program start" smoke test as an autopkgtest, to guard against
packaging failures like that.
Also adding support for autopkgtest to packages with an existing
testsuite that can run against the package as-installed is relatively
simple. It consists in adding a test control file, one or several
scripts to wrap the call to the testsuite and a source record header to
enable auto-discovery. Then on next upload your package will appear on
jenkins[1]
For example, in the case of simplejson (which is the package you're
referring to I suppose) the diff is quite small [2]
For reference the developer guide [3] explains the details.
[1] https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/
[2]
https://code.launchpad.net/~jibel/ubuntu/trusty/simplejson/enable_autopkgtest/+merge/195380
[3] http://developer.ubuntu.com/packaging/html/auto-pkg-test.html
Jean-Baptiste
--
IRC: jibel
--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
