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
Proven testers
At the QA weekly meeting of 2010-06-28[1], John Dulaney offered to work on combining the two proven testers pages (concerning joining the proven testers, and how to conduct testing) into a single page and provide a draft to the list for review. John subsequently submitted[2] his draft[3]. Adam Miller liked it[4].
Meanwhile, Adam Williamson proposed[5] activating the proven testers group before Bodhi was changed to activate the requirement for proven tester feedback, as a way to make sure the process worked smoothly and get in some 'practice'. The response was generally positive. The proposal was, however, overtaken by events. Luke Macken announced the next day[6] that a new version of Bodhi had been put in place which enabled the proven tester feedback requirement, so Adam quickly announced[7] the activation of the proven testers group and asked members to start testing immediately.
He also promised to start the ball rolling on the mentoring process, and sent out a proposal[8] the next day for a rough plan for proven tester mentoring. He suggested existing proven testers take sponsorship requests, ask the applicants to read the appropriate instructions, and then confirm that they are familiar with enabling updates-testing and posting feedback on updates, before sponsoring them into the proven testers group. Jesse Keating suggested[9] asking applicants in general to take the initiative and start reading instructions and providing feedback, and link to some of their feedback on their application ticket, so their membership could be quickly approved as soon as a mentor got around to looking at the ticket. Adam thought[10] this was a good idea, but felt that in practice it should be possible to personally pick up every current mentor request very quickly, given the number of requests and the number of existing proven testers.
Bob Lightfoot wrote about his proven tester testing process[11], in case it was of use to others, or anyone could suggest improvements for him. Till Maas suggested a simplication[12].
- ↑ http://fedoraproject.org/wiki/QA/Meetings/20100628
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091746.html
- ↑ http://fedoraproject.org/wiki/User:Jdulaney/Proven_Tester
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-July/091820.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091745.html
- ↑ http://lists.fedoraproject.org/pipermail/devel/2010-June/138008.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091781.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091793.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091794.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091800.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-July/091815.html
- ↑ http://lists.fedoraproject.org/pipermail/test/2010-July/091845.html
AutoQA
At the QA meeting, Will Woods reported that the AutoQA team was working on a helloworld test (a test test), which would exist to check that watchers and hooks - particularly the bodhi watcher and hook - work correctly. This is a prerequisite for the dependency check test, one of the major AutoQA priorities. Josef Skladanka said he had a test instance of the ResultsDB up and running on one of AutoQA's infrastructure machines, and had rewritten the initscripts and rpmlint tests to store their results in the database. He would continue to work on converting other tests. Kamil Paral announced that he had patched autoqa to use autotest labels correctly, which allows us to configure the actual running of tests in several ways - ensuring they are run on particular machine configurations. He pointed to a mailing list post[1] with a more detailed explanation.
Triage metrics
At the Bugzappers weekly meeting of 2010-06-29[1], Jeff Raber updated his progress with triage metrics. He had created a wiki page[2] to track his goals and progress, and had discussed some modifications to python-bugzilla with Will Woods. The group discussed the specific metrics Jeff was targeting, and made a few adjustments.
Request for old DeltaISOs
Andre Robatino asked[1] for anyone who had old DeltaISO files he had provided for various releases to seed the corresponding torrents so he could retrieve them, for the purpose of creating an archive of all previous DeltaISOs, making it easier to reconstruct particular test releases from the past whenever this might prove useful.
VERIFIED Bugzilla status
Aaron Farnes proposed an update[1] to the bug workflow wiki page[2] regarding the VERIFIED state. James Laska reviewed and approved his changes, which were also discussed at the weekly meeting. Aaron made it clear that triagers and reporters should manually set the status when they checked that a pending update would resolve an issue, leaving the Bodhi update system or the maintainer to close the bug.