#227: Document SOP for acceptance test event
--------------------+-------------------------------------------------------
Reporter: rhe | Owner: wutao85
Type: task | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Resolution: | Keywords:
--------------------+-------------------------------------------------------
Comment (by jlaska):
Perhaps linking to the rawhide acceptance test plan might help with the
*how* part of this
(https://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan).
While this is mostly documented in the test plan and I see the acceptance
test milestone primarily ...
1. to identify and resolve compose-related issues
2. file bugs for issues impacting the the rawhide acceptance test plan
3. find more bugs (early pre-TC1 testing)
We touch on #3 a bit in the F15 QA retrospective, so that's certainly an
area worth exploring for future test plan enhancement. Another thing I'd
like to see in the SOP is some discussion of exploratory testing. Using
the RATs images, I've been trying to find and file bugs which I suspect
will block or impact Alpha TC1 testing. Given the fix window between TC1
and RC1 is so short ... the earlier we can identify some of the bugs, the
better.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/227#comment:7>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
