On Mon, Jan 24, 2011 at 10:52:54AM +0800, Paul Wise wrote: > On Mon, Jan 24, 2011 at 7:19 AM, Iustin Pop <iustin@debian.org> wrote: > > > First, tests run during a package build are good, but they do not > > ensure, for example, that the package as installed is working OK. I've > > been thinking that (also) providing tests to be run after the package is > > installed (and not on the build results) would be most useful in > > ensuring that both the build process and the packaging is correct. > > Debian has definitely needed this for a long time. > > I'm thinking that these automated post-install tests are something > that all distributions could benefit from and probably we should push > them upstream. > > Automated post-install testing would be great, but it cannot apply in > all cases and should be complemented by README.test. I think both > approaches are needed. Agreed—I wasn't suggesting that README.test is not useful, just that there is potential for more in this area, at least for some class of packages. > For example: > > libwww-topica-perl: > […] > warzone2100: > […] Good examples, indeed. regards, iustin
Attachment:
signature.asc
Description: Digital signature