F12 critical path testing

[James Laska]

On Sun, 2010-10-10 at 22:09 -0500, Bruno Wolff III wrote:
> On Sun, Oct 10, 2010 at 18:49:10 -0400,
>   Timothy Davis <cpuobsessed at gmail.com> wrote:
> > When a critical path sits for any more than four weeks I suggest the
> > maintainer include test files and test cases
> > to help any tester. Things such as scripts/programs to test with, or
> > scenarios like do this and check that.
> 
> For example for squashfs, the bug was hard to test. Kevin saw it, but I
> didn't. We weren't sure exactly what changed that started breaking things
> for the nightly composes that Kevin is doing. I was more interested in
> making sure there weren't regressions than making sure that the bug was
> really fixed.
> 
> Having automated tests or even test plans would be useful for any package.
> But critical path packages are perhaps more worth doing this for. Maybe
> QA can slowly work through the list working with the package owners
> to try to develop reasonable tests.

This is great suggestion!  We've talked about spec'ing out some test
documentation for a subset of critpath packages, but just haven't had
the cycles yet.

If anyone is interested in getting started, I don't think we need more
than a draft wiki page to list some concise test instructions.  
I can see several ways to go here ... either create individual test
cases and grouping them in a category (see similar examples at
https://fedoraproject.org/wiki/Category:Test_Cases).  Alternatively, it
might be less wiki work to start noting tests on a single wiki page with
an eye towards turning it into a test plan (ala
https://fedoraproject.org/wiki/Category:Test_Plans).  My only suggestion
here would be that we eventually converge on a common format (whether
it's test cases, plans or something new).

Is there a critpath component(s) [1] someone might be interested in
starting with?  Howabout some heavy hitters that come up frequently,
like kernel, glibc, firefox etc...?

Thanks,
James

[1]
http://kojipkgs.fedoraproject.org/mash/branched-20101008/logs/critpath.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20101011/60ce0faa/attachment.bin