QA/Meetings/20090701

= Attendees =


 * Jóhann Guðmundsson (viking-ice)
 * Will Woods (wwoods)
 * Matthias Clasen (mclasen)
 * David Pravec (dpravec)
 * James Laska (jlaska)
 * Southern_Gentleman
 * Seth Vidal (skvidal)

Regrets:
 * Adam Williamson (adamw)
 * Jesse Keating (f13)

= Agenda =

Proposed meeting agenda

Previous meeting follow-up
I don't have big updates here, other than I finally dusted off my fingers and am getting started. I should have draft content soon. One of the pre-reqs for me was pulling together the test day feedback ... so having that done helps me now (https://www.redhat.com/archives/fedora-test-list/2009-July/msg00009.html).
 * [jlaska] - update QA/Goals wiki document
 * [viking_ice] - check-in with abrt

Viking_ice had to step away briefly. Looked into the abrt project over the week. Filed a RFE with several mock-ups designed to improve the bugzilla integration (see https://fedorahosted.org/abrt/attachment/ticket/53/Automatic%20Bug%20Reporting%20Tool%20Mockup1.png and https://fedorahosted.org/abrt/attachment/ticket/53/ABRT_simple_bug_filing_form.png)


 * [wwoods] - add post-install network test to basic functionality in rawhide acceptance plan

I added two cases to the plan, post-install network and post-install input. For additional information, please see https://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan#Basic_Functionality.

Fedora 12 Fit n Finish Test Days
Announcement: https://www.redhat.com/archives/fedora-test-list/2009-June/msg00741.html

mclasen briefed the team on the upcoming desktop-focused Fit_and_Finish test days. Traditional fedora test days focus on exercising upcoming features of the release. The goal of Fit'n'finish is to do a series of user-task focused test days, that are delivered with in the same manner as traditional Fedora test days. The first event will be this Tuesday (July 07, 2009) with a focus on Fit_and_Finish/Display_Configuration.

Southern_Gentleman asked if rawhide would be used for generating the live images? Mclasen indicated the plan is to use rawhide, but I don't think it is essential for user-task testing that everyone runs the same.

Viking_ice indicated that there aren't clear instructions on what to include in bug reports filed. Mclasen indicated he would add some clarity here after responding to the mail thread. Jlaska recommended linking to Category:Debugging and that the QA team could help fill information gaps.

AutoQA - update from wwoods
https://fedorahosted.org/autoqa

The QA:Rawhide_Acceptance_Test_Plan is complete. 7 out of 12 test cases created from the QA:Rawhide_Acceptance_Test_Plan.

The plan for next week:
 * have the test cases all finished
 * at least one automated

jlaska asked if there were any good candidates for tests that could be rapidly developed ... something off-the-shelf. Wwoods indicated there are a few good candidates, including:
 * the repodata/comps validity stuff
 * installer image existence

Wwoods indicated the need for reporting manual test results. Jlaska asked if this was intended as a generic test result reporting mechanism? Wwoods outlined he is trying to solve a specific problem of reporting test results for rawhide acceptance tests not yet automated, not rewrite a formal test case management system from scratch.

Install Testing SOP draft - update from lili
https://www.redhat.com/archives/fedora-test-list/2009-June/msg00734.html

Hopefully Liam is sleeping right now (being 12:44am for him) ... but wanted to give a quick update on an SOP he posted for review. Liam is trying to documenting the tasks involved when planning+preparing and executing a collaborative installation test event.

A few folks have chymed in already and helped clean up the wiki, so thanks to arxs and beland! While this largely affects the folks who have been testing RC's, feedback from a wider audience is encouraged ... as that's the audience we're hoping benefits from added transparency

Improve Bug Reporting proposal - update from viking_ice
https://fedoraproject.org/wiki/User:Johannbg/QA/Improve_reporting

Viking_ice discussed several explorations with the abrt tool and discussed several ideas on improving the user-interface. This included several mock-ups posted to the abrt trac instance (https://fedorahosted.org/abrt/attachment/ticket/53/Automatic%20Bug%20Reporting%20Tool%20Mockup1.png and https://fedorahosted.org/abrt/attachment/ticket/53/ABRT_simple_bug_filing_form.png).

Viking_ice suggested that abrt could be better if it were very similar to the simplified bugzilla reporting UI. This may reduce the learning curve

Mclasen suggested that several iterations would be needed to clean up the UI, and that assistance from the design team would certainly help.

Viking_ice also pointed to other efforts that improved the UI of setroubleshoot (see Design/SETroubleshootUsabilityImprovements). Specifically, the screenshots of the Report Bug screen.

Fedora Test Day Survey
Jlaska finally gathered F11 test day survey feedback and started posting recommendations for review. Please see https://www.redhat.com/archives/fedora-test-list/2009-July/msg00009.html

= Upcoming QA events =


 * 2009-07-07 - BugZappers/Triage_days
 * 2009-07-07 - Fit'n'Finish Display Configuration testing
 * 2009-07-08 16:00 UTC - Next QA Meeting QA/Meetings/20090708

= Action items =


 * [jlaska] - update QA/Goals wiki document

= IRC Transcript =

Generated by irclog2html.py 2.7 by [mailto:marius@pov.lt Marius Gedminas] - find it at mg.pov.lt!