updates improvements/changes ideas

Adam Williamson awilliam at redhat.com
Tue Nov 30 19:29:23 UTC 2010


On Tue, 2010-11-30 at 10:51 +0100, Michael Schwendt wrote:
> On Tue, 30 Nov 2010 09:31:31 +0100, Matthias wrote:
> 
> > On 29/11/10 19:08, Adam Williamson wrote:
> > > On Mon, 2010-11-29 at 12:40 -0500, James Laska wrote:
> > 
> > > Things that some people see as problematic are:
> > > 
> > > * Having to wait a week to push an update if you can't find testing
> > > * Testing being required for packages with automated test suites
> > > * The delay to security updates which is introduced by the testing
> > > requirements
> > 
> > Testing would get much easier, if packagers could provide some test
> > cases. The packager could send mail to -devel or -testing to get some
> > testers.
> 
> Sounds backwards to me. Given the life cycle of a bug, there is activity
> in bugzilla prior to the maintainer developing a fix. Plus, bodhi adds
> update notifications to bugzilla. If I were to expect someone to test the
> fix, it would be the bug reporter to be the additional tester.

Proven tester testing is not really about testing the bug fix contained
within an update; it's more about making sure the update doesn't cause
regressions, especially regressions that would negatively affect the
rest of the system.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net



More information about the test mailing list