User:Jlaska/Draft

The Fedora QA team would like your feedback on Fedora 11 Test Days. You may have seen Adam Williamson's planet post [1] kicking off Fedora 12 Test Day planning. We're interested in identifying areas for improvement to increase participation and improve effectiveness.

Please take 10-15 minutes to answer any/all of the questions below. You may reply to the mailing list, or send feedback directly to me. Your responses to this survey are instrumental in making Fedora 12 Test Days successful.

Many thanks to User:cward for his help in getting things moving with the survey questions!

Survey & Responses

1. How did you find out about Fedora Test Days?
   • devel mailing list
   • Fedora test mail list
   • Fedora project WiKi page of test day
   • Search for the nouveau feature in f11 and find out that a test day is planned
   • Through Planet Fedora and/or IRC.

1. Was sufficient documentation available to help you participate in a Fedora Test Day? If not, what did you find missing or in need of improvement?
   • Good example ... Test Day:2009-03-26 Nouveau
   • Bad example ... Test Day:2009-04-09 UEFI - how to identify if your system supports UEFI?
   • In all test cases I tried, concise but complete instructions were listed to help me test specific features or capabilities.

1. Did you encounter any obstacles preventing participation in Fedora test Days? How might they have been avoided?
   • HW, Time.
   • Failure while creating live images using Fedora 10 USB creator tools
   • Participants needed FAS account for wiki editing, but I know this was resolved.
   • For the tester,maybe downloading test media and burning them will save some time
   • Not directly to me, but I have read some complains about to represent the result in the wiki, because you need a FAS account and have the CLA done, with seams to be problematic for some users.
   • Access to hardware, but nothing you can do about that. :-) Some more indications about whether specific tests can be accurately performed in a KVM virtual guest would be appreciated, though.

1. Were you able to locate and download installation media for testing? Did it function as expected?
   • expected testing instructions on the live media to perform the tests without the need to setup an internet connection on the testing machine.
   • some bug report info gathering scripts would have been nice, that e.g. collect all the data required by the packages maintainers for a bug report in some file on the usb medium. E.g. the Xorg people wanted a lot of information that I did not have anymore after I rebooted to my stable F10 system and reported the bug.
   • Yes, now I know how to get installation media in the least amount of time. (download speed an issue)

1. What follow-up actions do you expect after the Test Day? Are your expectations currently being met?
   • The reported bugs should be fixed soon.
   • Some article with results on some Linux servers. I liked what jscotka written (in czech) about PowerManagement Testday: http://www.root.cz/clanky/jak-probihal-fedora-powermanagement-testday/
   • yes and no, the reported bugs are in touch with the developer, that's really good, but the issue is still there. But it's all right, because it seems hard to fix and effect no many people.
   • Typically I expected to be able to file my information through some input system (in this case, the wiki), and I assumed I would hear back if there were questions about the information I left or bugs I filed. The bugs I generated seemed to get the notice that was merited, so I feel my expectations were met.
   • If I were a new contributor to Fedora, an "attaboy" email might not be out of the question, though.

1. Would you participate again in future Fedora Test Days?
   • If they were planned better, then maybe I would be able to set aside time to do them. I would like to participate in future Test Days.
   • Would like to do so. Currently HW is one of the biggest blockers.

1. Do you have any more general comments or any suggestions for improving future test days?
   • start them earlier in rawhide development phase. If tens of bugs are found three weeks before freeze, we can hardly expect they are fixed in time.
   • If possible, can you announce the events (such as test day) in home page as news. When we open the home page we will know what is coming and what I can prepare to do, not like now, find them in thousands of mails
   • Set up a reporting center just for Test Day feedback. Using the wiki is definitely not good enough. Additionally, Do not limit the test days to people subscribed to the mailing list. Take a page from Mozilla's books and announce those test days to the world. Unfortunately, to do that, test days need to be planned better.
   • Better announcement of test days, also with more than 2 days ahead of time. Maybe some RSS feed only for test days or a calendar (iCal format maybe)
   • is there a way to document HOWTO run a test day, including how to make the required media and a template for the test day wiki page?