From Fedora Project Wiki

< QA‎ | Meetings

m (Small change)
m (Updates)
Line 55: Line 55:


There has been a lot of AutoQA activities in recent weeks, Jlaska asked the group to walk through some highlights.
There has been a lot of AutoQA activities in recent weeks, Jlaska asked the group to walk through some highlights.
Josef Skladanka updated the group on several AutoQA activities:
# Getting URLs of test results from AutoQA testruns is nearly finished.  Patches out for review on [https://fedorahosted.org/mailman/listinfo/autoqa-devel autoqa-devel@lists.fedorahosted.org]
# The beakerlib-based initscript test is now in production (see [https://fedorahosted.org/pipermail/autoqa-results/2010-April/016011.html sample results])
# Making progress on the resultsDB - We have finished the db schema (see [[AutoQA_resultsdb_schema]]) and accepted a input API (see [[AutoQA_resultsdb_API]])
# Next steps ...
#* Prototyping the resultsdb and using an XMLRPC based API to populate with results (jlaska, 16:06:12)
#* Creating a front-end which will be used for review/publish the data
Kamil Páral updated the group on his AutoQA focus areas:
# In addition to the notes above from Josef, working with Petr Splichal to automate the [[QA:Package_Sanity_Test_Plan]] (track plans using the [https://fedorahosted.org/autoqa/milestone/Package%20Sanity%20Tests autoqa PST milestone]).
# Package Sanity ensures clean install, removal, upgrade, etc of the packages (see [http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/package_sanity/examples/cheese-rpm-summary.txt;h=830a0a9311eb4e8442fd3858c0ad67ce694ad6c9;hb=refs/heads/pst sample test output]).  There is already a 'pst' script in the repository which you can try to perform sanity tests on a downloaded package or package in a repo.
# Next steps ...
#* detect that new updates are pushed to bodhi
#* download the package and all relevant packages
Will Woods provide some updates on his AutoQA focus areas:
# We have enough info about current bodhi to write a bodhi update watcher, but it may have some shortcomings and will soon be obsoleted
# We have a proposed storage encoding for putting test plan metadata in the wiki (see [[QA:Test_Plan_Metadata_Test_Page]]), this will be used by the resultsdb


== Open discussion - <Your topic here> ==
== Open discussion - <Your topic here> ==

Revision as of 13:40, 26 April 2010

Attendees

People present (lines said):

Regrets:

Agenda

  • [FIXME Proposed meeting agenda]
  • [FIXME MeetBot summary]

Previous meeting follow-up

  • jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org
    • Already completed by the infrastructure team, yay infrastructure!

See agenda below for additional follow-up items included in specific topics

Fedora 13 RC test status

Upcoming test milestones:

  • 2010-04-16 - Pre-RC Branched Acceptance Test Plan -- DELAYED, now INPROGRESS
  • 2010-04-23 - Final Blocker Meeting (f13blocker) #2 (recap)
  • 2010-04-29 - Test 'Final' Test Compose
  • 2010-04-30 - Final Blocker Meeting (f13blocker) #3
  • 2010-05-05 - Final Blocker Meeting (f13blocker) #4
  • 2010-05-06 - Test 'Final' RC

Upcoming test days:

Fedora 13 QA Retrospective
Ideas have already been coming in since F-13-Alpha. It's not too early to note QA issues you felt where handled well, or could have been improved. Your ideas will be used during F-14 QA goal planning. Voice your comments at Fedora_13_QA_Retrospective.

Bodhi QA workflow status check-in

https://fedorahosted.org/bodhi/milestone/2.0

Proventesters check-in

Package Acceptance Test Plan check-in

AutoQA check-in

There has been a lot of AutoQA activities in recent weeks, Jlaska asked the group to walk through some highlights.

Open discussion - <Your topic here>

Upcoming QA events

Action items

IRC Transcript

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20100426&oldid=169045"