Ticket #57 (closed task: fixed)

Opened 4 years ago

Last modified 4 years ago

Proposed Test Day - Virtualization

Reported by: jforbes Owned by:
Priority: major Milestone: Fedora 13
Component: Test Day Version:
Keywords: Cc: llim@…, mjenner@…, tyan@…, ndai@…, xwang@…, mdoyle@…
Blocked By: Blocking:

Description

I will be more than happy to plan/host the test day.

Preferred times are 2010-04-08 or 2010-04-15 or any other available day before between the alpha release and then.

https://fedoraproject.org/wiki/Category:F13_Virt_Features for features to be tested.

Change History

comment:1 Changed 4 years ago by adamwill

Hey Justin, thanks for the suggestion!

To grab the date you want, just add your event to the schedule following the format of the other days, there's no formal acceptance procedure, it's first come first served :)

For info on the process of setting up the test day, see:

https://fedoraproject.org/wiki/QA/SOP_Test_Day_management

let us know if you get stuck at any point, or would like any help with the PR or anything. thanks!

comment:2 Changed 4 years ago by jlaska

Justin, the category page provides a good list of features that would make prime candidates for the test day (VirtioSerial?, VHostNet, Hostinfo, VirtAuth?, VNCVNCTunnel). However, there are several features listed as incomplete (< %30 implemented). Are these features still planned for F13?

comment:3 Changed 4 years ago by beland

Though I think the main thrust is to find new bugs, if people are looking for things to test, they can help triage and attempt to reproduce existing bugs:

https://fedoraproject.org/wiki/Virtualization_bugs

These bugs highlight areas of potential weak code, and it's also helpful to know whether they are present in the latest code.

There's also one of my own bugs which may block some types of testing entirely:

https://bugzilla.redhat.com/show_bug.cgi?id=523981

It's filed against the kernel, and I'm not sure that's correct, nor do I really know how widespread this problem is.

comment:4 Changed 4 years ago by jlaska

  • Cc llim@…, mjenner@…, tyan@…, ndai@…, xwang@… added

comment:5 Changed 4 years ago by jlaska

  • Cc mdoyle@… added

comment:6 follow-up: ↓ 7 Changed 4 years ago by jlaska

The test day is scheduled for this Thursday (2 days from now). A skeleton wiki page is in place, but I don't see many test cases assigned to the different features yet (see wiki).

Are there any areas you'd like help defining test cases for? If time is too short for creating test cases, I would suggest cancelling or postponing the test event to allow for more preparation.

comment:7 in reply to: ↑ 6 Changed 4 years ago by jforbes

Replying to jlaska:

Are there any areas you'd like help defining test cases for? If time is too short for creating test cases, I would suggest cancelling or postponing the test event to allow for more preparation.

Test cases are covered, the wiki will be complete this afternoon. The only other prep that has not been tackled yet is making test live images.

comment:8 Changed 4 years ago by kparal

jforbes: if the nightly composes [1] are not satisfactory, I can help you with creating custom live images (custom set of packages, or some additional packages from your own repo), if you don't know how to do it. Just contact me tomorrow at latest (UTC+2).

[1] http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/

comment:10 follow-up: ↓ 12 Changed 4 years ago by llim

I have noticed that the Test Cases are on the wiki. Is there anything else we need to do/prepare??

comment:11 Changed 4 years ago by jforbes

The last step is to prepare/test/upload the live image ISOs for test day, I am doing that right now.

comment:12 in reply to: ↑ 10 Changed 4 years ago by jlaska

Replying to llim:

I have noticed that the Test Cases are on the wiki. Is there anything else we need to do/prepare??

Some of the tests are not in an easily digestable format. I would recommend using the test case wiki template where possible (https://fedoraproject.org/wiki/Template:QA/Test_Case), and also categorizing tests appropriately (https://fedoraproject.org/wiki/Category:Virtualization_Test_Cases). I've started cleaning a few tests up already, but some additional tests could use similar cleanup. For example:

comment:14 Changed 4 years ago by rhe

  • Resolution set to fixed
  • Status changed from new to closed

Test day is over, thanks for everyone's hard work. A summary of this can be found at:

http://lists.fedoraproject.org/pipermail/test/2010-April/090245.html

Note: See TracTickets for help on using tickets.