QA/Meetings/20110103

Attendees

People present (lines said)

Unable to attend:

1. Rhe (hopefully sleeping)
2. Hongqing (hopefully sleeping)

Agenda

• Proposed meeting agenda
• [FIXME MeetBot summary]

Previous meeting follow-up

1. 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)

Hurry and Alam scheduled another l10n/i18n test day (see https://fedorahosted.org/fedora-qa/ticket/158)

Next steps ...

1. Schedule systemd event?
2. Contribute ideas to Talk:QA/Fedora_15_test_days
3. Identify owners to organize and host test days

Requirements review for Fedora test case management

Owner

rhe

Summary

See fedora-qa ticket#152 -- Requirements review for Fedora test case management

Hurry drafting requirements at Rhe/tcms_requirements_proposal

Use case identification -- see https://fedoraproject.org/wiki/Rhe/tcms_use_cases

Use case comparison -- see https://fedoraproject.org/wiki/Rhe/tcms_Comparison

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 drafing wiki pages intended to document the process, expects updates shortly

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)

Team decided to serialize depcheck tests to avoid complexity relating to handling multiple depcheck tests running at the same time

Depcheck data - during busiest-ever month, we would need depcheck (on average) once every 33 minutes. Depcheck currently takes <= 1m to complete

mkrizek finished up autoqa staging support (pushed to mkrizek-staging)

mkrizek starting logging support to better capture output from watchers and 'autoqa'

jlaska posted updates to clumens anaconda branch - improved checkbot.sh test, new compose-tree pungi test, and initial post-git-receive watcher to trigger events on git push

Next steps ...

1. Wwoods posting blog article explaining the need for autoqa ticket#248
2. Determine appropriate strategy for watcher and depcheck integration, and revise patchset as needed
3. Merge clumens branch into master