[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

2009-06-24 - Fedora QA meeting Recap



Full IRC transcript available at
https://fedoraproject.org/wiki/QA/Meetings/20090624.

= Attendees =

* (Southern_Gentlemen)
* Jóhann Guðmundsson (viking-ice)
* Will Woods (wwoods)
* Seth Vidal (skvidal)
* James Laska (jlaska)
* John Poelstra (poelcat)

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

= Agenda =

[https://www.redhat.com/archives/fedora-test-list/2009-June/msg00652.html Proposed meeting agenda]

== Previous meeting follow-up ==

* [jlaska] - update [[QA/Goals]] wiki document
No traction over the last week.  Still a high priority item for jlaska.
Lot's great things happening in QA, and some common themes around them.
Just looking for a concise way to document those efforts into a single
page.

* [wwoods] - updates on Rawhide acceptance test plan

Test plan:
https://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan created.
Some feedback on fedora-test-list helped shape the list of tests to
include.  

Viking_ice asked if we forgot to include a test for network connectivity
as a basic functionality test?  

== Fedora 12 QA schedule changes ==

https://www.redhat.com/archives/fedora-test-list/2009-June/msg00507.html

* wwoods asked if additional blocker bug days were listed
* Viking_ice and jlaska both were on the fence with regards to whether
or not to include test days in the formal Fedora schedule.  Viking_ice
suggested test days need more flexibility currently when it comes to the
schedule.
* poelcat hilighted the second change in the schedule around compose
checkpoints during each milestone.  

The next step will be to propose the schedule changes to rel-eng.  If
approved, we then work to plan around the changes.

== AutoQA - update from wwoods ==

https://fedorahosted.org/autoqa

Wwoods provided an update on where the autoqa project is.  Real Soon Now
we'll be trying to write some test code and wikifying what we learn
about writing tests for autotest.  I expect next meeting (or the one
after that) we may have some test code and/or results to show and a list
of cases we need help writing.

Additionally, writing test cases in the wiki has already started and
will be ongoing.

Wwoods intends to solicit volunteers to help with defining test cases,
and once defined, automating the test cases.  Anyone with a little
python skill can likely contribute.

== Test Day SOP draft - update from awilliam ==

Adamw was unable to make the meeting, but sent a quick update to the
mailing list on a Fedora Test Day SOP document.  Adam's draft email can
be found
https://www.redhat.com/archives/fedora-test-list/2009-June/msg00662.html.  Please pass along any constructive feedback to the mailing list.

== Improve Bug Reporting proposal - update from viking_ice ==

https://fedoraproject.org/wiki/User:Johannbg/QA/Improve_reporting

Viking_ice introduced several topics noted in the above document.  All
topics outline areas where improvements could be made around bug
reporting.  

Viking_ice provided good news for those concerned about the look'n'feel
of the bugzilla reporting page.  Bugzilla-3.4 intends to simplify this
view (see
http://lpsolit.wordpress.com/2009/05/24/simpler-form-to-file-bugs-in-bugzilla-3-4/).

Jlaska asked what specific feedback viking_ice was interesting in, and
suggested possibly teaming up with the BugZappers since several of the
proposed ideas line up with BugZapper goals.

Viking_ice asked whether the abrt tool could be used to improve bug
reporting. 

Viking_ice summarized by saying ''we need to come up with some plans on
how to gather the info from maintainers on what they want on their
reports on how to get that info from them.'' and pointed to
[[User:Johannbg/QA/Kernel]] as an example based on j-rod's suggestion
from the Fedora 11 retrospective meeting.

Jlaska suggested having a way to catalog content (e.g. debugging tips,
or bug filing tips) for testers to easily find could be a great start.

== Open discussion ==

=== Target Audience for israwhidebroken.com? ===

Viking_ice asked who are the target audience with israwhidebroken.com
and what is being hope to accomplish with that?   Adding that we, as
testers, know that rawhide is largely broken before beta.

Jlaska suggested pulled content from the [[Israwhidebroken.com_Proposal|
IRB.COM FAD proposal]] ... ''Provide a single, well-known location with
information about whether or not Rawhide is broken, and a link to the
last known-good Rawhide tree.''  Jlaska summarized, ''for me ... it's
all about consistently gathering data to facilitate decision making.''

= Upcoming QA events =

* 2009-06-30 - [[BugZappers/Triage_days]]
* 2009-07-01 16:00 UTC - Next QA Meeting [[QA/Meetings/20090701]]

= Action items =

* [viking_ice] - check-in with abrt 
* [wwoods] - add post-install network test to basic functionality in
rawhide acceptance plan
* [jlaska] - update [[QA/Goals]] wiki document

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]