From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 05:53, 28 July 2011 by Adamwill (talk | contribs) (create fwn 283 qa beat)

QualityAssurance

In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].

Contributing Writer: Adam Williamson

  1. ↑ http://fedoraproject.org/wiki/QA
  2. ↑ http://fedoraproject.org/wiki/QA/Join

Test Days

The Fedora 15 Test Day track is now finished, and the main Fedora 16 Test Day track has not yet started. If you would like to propose a main track Test Day for the Fedora 16 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[1]. At the weekly group meeting of 2011-07-18[2], the group agreed to delay the planned Fedora 15 on Amazon EC2 Test Day on 2011-07-19, as the images would not be ready in time. Adam Williamson pencilled in the X Test Week for 2011-08-30 to 2011-09-01[3], and Jaroslav Škarvada proposed a power management Test Day for 2011-09-29[4]. Adam sent out a call for Test Days[5].

  1. ↑ http://fedorahosted.org/fedora-qa/
  2. ↑ http://fedoraproject.org/wiki/QA/Meetings/20110718
  3. ↑ http://fedorahosted.org/fedora-qa/ticket/223
  4. ↑ http://fedorahosted.org/fedora-qa/ticket/225
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101393.html

oVirt node spin review and testing

At the weekly meeting, the group held an initial discussion of the proposed oVirt node spin[1], from the standpoint of whether to grant it QA approval. Athmane Madjoudj volunteered to work on making sure the necessary testing framework was in place. By 2011-07-22, he had a draft validation matrix[2] ready for review[3].

  1. ↑ http://fedoraproject.org/wiki/Ovirt_Node_Spin
  2. ↑ http://fedoraproject.org/wiki/User:Athmane/Draft_Ovirt_Node_validation_matrix
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101439.html

QA group meeting SOP

James Laska announced[1] that he had put the draft group meeting SOP (see FWN #282) into production[2].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101358.html
  2. ↑ http://fedoraproject.org/wiki/QA:SOP_IRC_meeting_process

Separation of release validation and feature processes

At the FESCo meeting of 2011-07-18[1], FESCo approved the group's proposal (see FWN #282) to formalize the separation between the release validation and feature processes. Adam Williamson subsequently announced that he had made the necessary changes to the wiki[2].

  1. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-07-18/fesco.2011-07-18-17.01.log.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101368.html

Fedora 16 Alpha RATs run

Tao Wu announced the completion of the first RATs (Rawhide Acceptance Tests) automated installation testing run for Fedora 16 Alpha[1]. He reported that the testing failed due to a major bug in installation[2].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101376.html
  2. ↑ http://bugzilla.redhat.com/show_bug.cgi?id=723144

Instalatron anaconda testing framework

Sergio Rubio of FrameOS[1] wrote to let the group know[2] of the release of Instalatron[3], a testing framework for anaconda based around VirtualBox input automation and ImageMagick image comparison. James Laska replied to thank Sergio for reaching out, and to point out the similar work being done by Tao Wu and Hongqing Yang to automate the Fedora installation validation matrix[4]. Tim Flink asked some questions about the design of Instalatron[5], and Sergio provided some answers[6]. Eric Blake noted that KVM had recently grown the ability to inject keyboard scancodes[7], which Sergio had cited as the main reason for choosing VirtualBox. David Cantrell gave a heads-up that the design of anaconda would soon change quite drastically[8], and James recommended the use of AT-SPI in preference to image analysis[9]. Sergio thanked everyone for their feedback[10].

  1. ↑ http://frameos.org
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101384.html
  3. ↑ http://github.com/abiquo/instalatron
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101385.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101387.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101399.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101400.html
  8. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101415.html
  9. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101416.html
  10. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101417.html

Release criteria updates

James Laska followed up his initial survey of ways to handle secondary architecture release criteria (see FWN #281) with a draft[1] of the preferred approach[2].

James also proposed some changes to the criteria following from the second Alpha blocker bug review meeting[3].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101431.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101431.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-July/101446.html

AutoQA

James Laska wondered if it would be possible to run depcheck tests on EPEL packages[1]. Kamil Paral said it had not been tried yet, and had some questions about the benefits. He summarized that "Overall it should be doable, but it requires quite some work and resources."[2]. James said he would check if it was the EPEL SIG or individual maintainers who were interested[3].

Josef Skladanka posted[4] a "brain dump" of ideas he and Kamil had come up with around depcheck[5].

Kamil proposed (and later carried out) the inclusion of a NEWS file in the AutoQA source[6], and provided a draft[7].

The group continued to work on several tasks related to making AutoQA output more attractive and legible[8] [9] [10].

  1. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002615.html
  2. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002616.html
  3. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002621.html
  4. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002620.html
  5. ↑ http://fedoraproject.org/wiki/User:Jskladan/Sandbox:Depcheck
  6. ↑ http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002622.html
  7. ↑ http://kparal.fedorapeople.org/autoqa/NEWS
  8. ↑ http://fedorahosted.org/autoqa/ticket/351
  9. ↑ http://fedorahosted.org/autoqa/ticket/359
  10. ↑ http://fedorahosted.org/autoqa/ticket/361
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=247404"