On Wed, Dec 15, 2010 at 12:25:21PM +0100, Martin Pitt wrote: > Matt Zimmerman [2010-12-15 11:11 +0000]: > > Works for me. The important thing is that we have assurance that the tests > > pass on the build we're going to ship to users. Running the tests during > > the build is just the simplest way to manage that assurance, but if it can > > be provided by other means, that should be sufficient. > > It doesn't prevent e. g. forgetting to actually install new files > from a new version in debian/*.install, putting them into the wrong > destination path, or a problem with the python integration. So for SRU > verification I'm actually more interested in testing the actually > installed .deb.
I agree that it's more valuable to test the installed .deb. However, that shouldn't require a dependency on python-testtools, should it? That package would only be needed when running the tests, and could be installed in the testing environment. I thought we were talking about build-time tests. -- - mdz -- technical-board mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/technical-board
