<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Good idea, me thinks.<br><br><br>> Subject: Proven tester special testing procedures: PackageKit?<br>> From: awilliam@redhat.com<br>> To: test@lists.fedoraproject.org<br>> Date: Thu, 29 Jul 2010 14:01:36 -0700<br>> <br>> We've talked about special proven testers testing procedures for<br>> kernels, and now another candidate for special test procedures has<br>> emerged: PackageKit. A bug in PackageKit got out in a Fedora 13 update<br>> which broke update notification, which is obviously a big problem.<br>> PackageKit isn't actually on the critical path for F13, but it is for<br>> F14 and up.<br>> <br>> So, I'd like to propose a special testing procedure for updates to<br>> PackageKit (actually, any package management-related critpath update<br>> should be tested in this way). As well as testing package installation,<br>> we should test update notification and installation for such updates. We<br>> can consider different ways of doing this, but an easy way would be<br>> simply to 'yum downgrade' an installed package, then wait: within a<br>> short time (I'll have to check how long with Richard, I think 30 minutes<br>> or an hour), an update notification should appear to let you know an<br>> update is available to that package. If not, we have problems.<br>> <br>> If everyone thinks this makes sense, I'll propose a wiki draft which<br>> sets up a system for package-specific testing procedures and drafts such<br>> a procedure for PackageKit. What does everyone think of this? Thanks!<br>> -- <br>> Adam Williamson<br>> Fedora QA Community Monkey<br>> IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org<br>> http://www.happyassassin.net<br>> <br>> -- <br>> test mailing list<br>> test@lists.fedoraproject.org<br>> To unsubscribe: <br>> https://admin.fedoraproject.org/mailman/listinfo/test<br> </body>
</html>