From Fedora Project Wiki
m (→Agenda) |
m (FIXME) |
||
Line 8: | Line 8: | ||
= Agenda = | = Agenda = | ||
* [http://lists.fedoraproject.org/pipermail/test/2010-December/096075.html Proposed meeting agenda] | * [http://lists.fedoraproject.org/pipermail/test/2010-December/096075.html Proposed meeting agenda] | ||
* [ | * [http://meetbot.fedoraproject.org/fedora-meeting/2010-12-20/fedora-qa.2010-12-20-16.00.html MeetBot summary] | ||
== Previous meeting follow-up == | == Previous meeting follow-up == |
Revision as of 16:46, 20 December 2010
Attendees
People present (lines said)
Unable to attend:
- Rhe (hopefully sleeping)
Agenda
Previous meeting follow-up
- jlaska to ping jens+rhe and Alam for thoughts on a F15 l10n/i18n test day
- jlaska to merge User:Bruno#Mockup_for_QA_-_Tracking_bug_queries into QA:SOP_Blocker_Bug_Meeting
- Bodhi feedback patch from fcami (see
infrastructure ticket#701
awaiting review
Call for Test Days
- Owner
- AdamW
- Summary
- Call for ideas/owners for Fedora 15 QA/Test_Days
- Monitor list of approved features for ideas
- Several events scheduled so far (GNOME 3, Xfce 4.8 and X Test Week)
- Next steps ...
- Contribute ideas to Talk:QA/Fedora_15_test_days
- Identify owners to organize and host test days
- Schedule another l10n/i18n test day
Python script communicating with bugzilla
- Owner
- Bruno
- Summary
- Tune existing python scripts to detect UNTESTED blocker bugs
- Bruno drafted a set of sample queries, see User:Bruno#Mockup_for_QA_-_Tracking_bug_queries
- The team discussed different approaches for how to integrate this list into current process
- Next steps ...
- The team tentatively agreed to review the list in each blocker review meeting
- jlaska going to merge the proposed queries into the Blocker meeting SOP
Requirements review for Fedora test case management
- Owner
- rhe
- Summary
- See
fedora-qa ticket#152
- Requirements review for Fedora test case management
- Hurry started drafting requirements at Rhe/tcms_requirements_proposal
- Next steps ...
- Hurry will continue refining requirements
- All - please review and add any comments/concerns in Talk page
Critical Path test case development
- Owner
- adamwill
- Summary
- See
fedora-qa ticket#154
- Still experimenting with some mock-ups/examples
- Next steps ...
- AdamW planning to mail the list explaining proposed system and linking to examples
AutoQA Update
- Owner
- kparal
- Summary
- clumens' anaconda_storage test has been reviewed and ready to land in git master branch
- The patch representing second attempt for solving ticket #205 has landed into autoqa-devel. That means we will be able to send our test results as comments into Bodhi.
- lmacken enabled us to use staging Bodhi instance for AutoQA development purposes (mainly he turned off email notifications). Kudos to him for that
- mkrizek and I worked on ticket #241 [6] ("Add support for a staging server"). The patch is not posted yet (waiting for previous patch to land in master), but the code is available at mkrizek-staging branch
- jskladan works on a different kind of a koji watcher. His work is available in the 'new_koji_watcher' branch. His work should enable us to hook up depcheck properly into our framework. Some discussion followed on how best to group -pending updates, the group agreed to discuss offline
- wwoods still working on a blog post and code to handle ticket #248 (simultaneous depcheck test runs)
- Next steps ...
- Wwoods posting blog article explaining the need for
autoqa ticket#248
- Determine appropriate strategy for watcher and depcheck integration, and revise patchset as needed