FWN/Beats/QualityAssurance: Difference between revisions

Revision as of 22:03, 30 June 2010

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

Test Day process improvements

A message^[1] from James Laska prompted a wide discussion of possible improvements to the Test Day process to improve participation. James asked^[2] if the group was trying to run too many events and not dedicating sufficient time to each, but Adam Williamson did not think so^[3].

Jóhann Guðmundsson suggested^[4] extending the test period to a week and broadening the coverage of each event. Adam felt the concurrency aspect of a single day to bring testers and developers together in real-time was valuable, but thought Jóhann had a valuable point in that the group could do a better job of making it clear to potential testers that testing performed outside of the Test Day is still valuable. Jeff Raber made some concrete suggestions^[5] as to how this could be achieved, and Adam implemented them^[6].

Jeff also suggested changing the name of the events, though Adam mentioned in his reply that he had not been able to think of anything that improved on 'Test Day'. Eric Blake suggsted^[7] 'Test Blitz', James contributed^[8] 'Bug Day' and Jóhann favored^[9]'Test Sprint'. Adam jokingly proposed a poll^[10], and added some wider-ranging thoughts about how the process could be re-organized to provide greater opportunities for participation and publicity while not losing the aspect of concurrency.

Proven testers

After several more revisions following the work mentioned in last week's issue, Aaron Farnes announced^[1] that the proven testers instruction page had been moved to the main wiki space^[2]. Several people replied to congratulate Aaron on the clarity of the page.

New desktop release criteria

Adam Williamson proposed^[1] several new release criteria, as a result of his discussions with the various desktop SIGs. These would cover session management tasks, update notification, and keyring functionality.

↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091702.html

Fedora 14 recommendations

James Laska announced^[1] that he had filed a group of trac tickets covering the recommendations for the Fedora 14 cycle which had derived from the Fedora 13 retrospective discussed in previous issues.

↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091663.html

[1] ttp://fedoraproject.org/wiki/QA

[2] ttp://fedoraproject.org/wiki/QA/Join

[3] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091564.html

[4] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091567.html

[5] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091571.html

[6] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091566.html

[7] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091575.html

[8] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091576.html

[9] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091585.html

[10] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091590.html

[11] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091592.html

[12] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091593.html

[13] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091625.html

[14] ttp://fedoraproject.org/wiki/Proven_tester

[15] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091702.html

[16] ttp://lists.fedoraproject.org/pipermail/test/2010-June/091663.html

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[1]

[2]

[1]

[1]

@@ Line 8: / Line 8: @@
 <references/>
-=== Proven testers ===
+=== Test Day process improvements ===
-During the QA weekly meeting of 2010-06-14<ref>http://fedoraproject.org/wiki/QA/Meetings/20100614</ref>, [[User:Adamwill|Adam Williamson]] reported that he had drafted a set of instructions<ref>http://fedoraproject.org/wiki/User:Adamwill/Draft_proventesters_instructions</ref> for proven testers (under the new proven tester policy<ref>http://fedoraproject.org/wiki/QA/JoinProvenTesters</ref>), and also had updated various wiki pages<ref>http://fedoraproject.org/wiki/QA</ref> <ref>http://fedoraproject.org/wiki/QA/Join</ref> <ref>http://fedoraproject.org/wiki/QA/Updates_Testing</ref> to reference the proven testers process. [[User:Jlaska|James Laska]] noted that he was monitoring the ticket<ref>http://fedorahosted.org/bodhi/ticket/424</ref> requesting the infrastructure team to configure Bodhi to require proven tester feedback on critical path updates. Adam subsequently announced his draft on the mailing list<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091513.html</ref>, followed by a second draft<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091552.html</ref>. Aaron Faanes stepped in<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091559.html</ref> with a much-improved revision of Adam's draft<ref>https://fedoraproject.org/wiki/User:Dafrito/Draft_proventesters_instructions</ref>. Adam replied<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091560.html</ref> to thank Aaron for his improvements.
+A message<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091564.html</ref> from [[User:Jlaska|James Laska]] prompted a wide discussion of possible improvements to the Test Day process to improve participation. James asked<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091567.html</ref> if the group was trying to run too many events and not dedicating sufficient time to each, but [[User:Adamwill|Adam Williamson]] did not think so<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091571.html</ref>.
-=== AutoQA  ===
+[[User:Johannbg|Jóhann Guðmundsson]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091566.html</ref> extending the test period to a week and broadening the coverage of each event. Adam felt the concurrency aspect of a single day to bring testers and developers together in real-time was valuable, but thought Jóhann had a valuable point in that the group could do a better job of making it clear to potential testers that testing performed outside of the Test Day is still valuable. [[User:Jraber|Jeff Raber]] made some concrete suggestions<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091575.html</ref> as to how this could be achieved, and Adam implemented them<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091576.html</ref>.
-During the QA meeting, [[User:Kparal|Kamil Paral]] reported that the AutoQA team had decided to re-prioritize their goals with the aim of delivering concrete results as soon as possible, even where this meant not immediately meeting the whole range of aims for the project<ref>http://fedorahosted.org/pipermail/autoqa-devel/2010-June/000668.html</ref>. They had decided the current priorities were to test and finish the Bodhi hook, implementing the ability to run potentially dangerous tests in a virtual machine, creating a test instance of the autotest environment for testing new features without breaking the stable instance, getting a publicly accessible machine for the results database (resultdb), and working on resultdb.
+Jeff also suggested changing the name of the events, though Adam mentioned in his reply that he had not been able to think of anything that improved on 'Test Day'. [[User:Ericb|Eric Blake]] suggsted<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091585.html</ref> 'Test Blitz', James contributed<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091590.html</ref> 'Bug Day' and Jóhann favored<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091592.html</ref>'Test Sprint'. Adam jokingly proposed a poll<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091593.html</ref>, and added some wider-ranging thoughts about how the process could be re-organized to provide greater opportunities for participation and publicity while not losing the aspect of concurrency.
 <references/>
-=== Critical path wiki update ===
+=== Proven testers ===
-[[User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091517.html</ref> that he had revised the critical path documentation on the Wiki. He had created a new page<ref>http://fedoraproject.org/wiki/Critical_Path_Packages</ref> to complement the existing critical path proposal page<ref>http://fedoraproject.org/wiki/Critical_Path_Packages_Proposal</ref>, which had initially been only the proposal of the critical path process but had come to be used as a general reference for the implemented process as well.
-<references/>
-=== Kernel triage ===
-During the Bugzappers weekly meeting of 2010-06-15<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-06-15/bugzappers.2010-06-15-15.01.log.html</ref>, [[User:Tcpip4000|JP]] reported that he had updated the stock responses on the older kernel triage page<ref>http://fedoraproject.org/wiki/KernelBugTriage and BugZappers</ref> to match the style of the newer Bugzappers stock responses<ref>http://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses</ref>, and asked for feedback on the changes.
-<references/>
-=== Triage metrics ===
-During the Bugzappers meeting, [[User:jraber|Jeff Raber]] reported his progress on the new triage metrics project. He had created a Bugzilla query<ref>http://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=BugsTriaged-Last30Day&sharer_id=292687</ref> which lists bugs triaged in the previous 30 days, and was working on some modifications to python-bugzilla to provide output suited to triage statistics. [[User:Adamwill|Adam Williamson]] promised to put Jeff in touch with [[User:Wwoods|Will Woods]] to discuss merging the python-bugzilla changes.
+After several more revisions following the work mentioned in last week's issue, Aaron Farnes announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091625.html</ref> that the proven testers instruction page had been moved to the main wiki space<ref>http://fedoraproject.org/wiki/Proven_tester</ref>. Several people replied to congratulate Aaron on the clarity of the page.
 <references/>
-=== Setting needinfo on impending end-of-life bugs ===
+=== New desktop release criteria ===
-During the Bugzappers meeting, [[User:Mcepl|Matej Cepl]] suggested that when adding a comment to bugs on releases that will soon go end-of-life, we should also set the needinfo state to mark that additional input is needed to keep the bug open. After some discussion, everyone agreed that this was a good idea.
+[[User:Adamwill|Adam Williamson]] proposed<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091702.html</ref> several new release criteria, as a result of his discussions with the various desktop SIGs. These would cover session management tasks, update notification, and keyring functionality.
 <references/>
@@ Line 44: / Line 32: @@
 === Fedora 14 recommendations ===
-[[User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091538.html</ref> the list of recommendations for the Fedora 14 cycle based on the Fedora 13 QA retrospective<ref>http://fedoraproject.org/wiki/Fedora_13_QA_Retrospective#Recommendations</ref>. He noted that the next task would be to organize the recommendations into a set of trac tickets to track their implementation.
+[[User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091663.html</ref> that he had filed a group of trac tickets covering the recommendations for the Fedora 14 cycle which had derived from the Fedora 13 retrospective discussed in previous issues.
-<references/>
-=== Reopening bugs ===
-Matt McCutchen brought up the topic<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091541.html</ref> of reopening bugs, specifically the fact that most Bugzilla users can only reopen bugs that they filed (or which are assigned to them). He mentioned that he had filed an RFE asking that all users be given permission to reopen bugs<ref>http://bugzilla.redhat.com/show_bug.cgi?id=573535</ref>. [[User:Adamwill|Adam Williamson]] said<ref>http://lists.fedoraproject.org/pipermail/test/2010-June/091546.html</ref> he would forward the proposal to the Bugzilla maintainers for consideration.
 <references/>

Search