[Fedora QA] #219: Create virtualization installation validation test cases
by fedora-badges
#219: Create virtualization installation validation test cases
-----------------------------------------+----------------------------------
Reporter: adamwill | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 16
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
As per the Beta criteria survey in https://fedorahosted.org/fedora-
qa/ticket/151 , there are no test cases to enforce the Beta release
criteria:
"The release must boot successfully as a virtual guest in a situation
where the virtual host is running the same release (using Fedora's current
preferred virtualization technology)"
"The release must boot successfully as a virtual guest in a situation
where the virtual host is running the previous stable Fedora release
(using Fedora's current preferred virtualization technology)"
"The release must boot successfully as a virtual guest in a situation
where the virtual host is running a supported Xen implementation"
We should create test cases to explicitly cover these criteria, especially
the Xen one, which we do not usually test at present (the other two
usually get covered in practice, although we don't have explicit test
cases for them).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/219>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #244: Cloud SIG Test Day
by fedora-badges
#244: Cloud SIG Test Day
----------------------+-----------------------------------------------------
Reporter: rbergero | Owner:
Type: defect | Status: new
Priority: major | Milestone: Fedora 16
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
At bare minimum right now:
* Fedora EC2 images
* OpenStack
We'd like the last slot, on 10/20.
-Robyn
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/244>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #230: QA:Testcase_Anaconda_autopart_(encrypted)_install overlaps with QA:Testcase_base_startup
by fedora-badges
#230: QA:Testcase_Anaconda_autopart_(encrypted)_install overlaps with
QA:Testcase_base_startup
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
See summary. With the new 'base' matrix, I made startup a separate 'base'
test - it's not really part of installer testing. The
QA:Testcase_Anaconda_autopart_(encrypted)_install includes startup
testing. I think it'd be best to shorten that test case, and make a note
in it that testing whether the installed system successfully boots is part
of the base_startup test.
assigning to me, but if anyone else wants to take over, go for it...
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/230>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #220: Review RHBZ #704030 with rel-eng to identify cause and make appropriate SOP changes to ensure issue is not repeated
by fedora-badges
#220: Review RHBZ #704030 with rel-eng to identify cause and make appropriate SOP
changes to ensure issue is not repeated
----------------------+-----------------------------------------------------
Reporter: jdulaney | Owner: jdulaney
Type: defect | Status: new
Priority: major | Milestone: Fedora 16
Component: Trac | Version:
Keywords: |
----------------------+-----------------------------------------------------
During the media creation process, if --excludes is not explicitly in the
repo definition, then packages get pulled in that cause package conflicts.
For example, astronomy-bookmarks-1-7.fc15.noarch xor fedora-
bookmarks-15-0.1.noarch, but not both.
There needs to be a patch for rel-eng to specify that this be done and
checked for every time a release/release candidate is composed.
This is to follow with the Alpha Release Criterion:
"There must be no file conflicts (cases where the files in some packages
conflict but the packages have explicit Conflicts: tags are acceptable) or
unresolved package dependencies during a media-based (CD/DVD) install "
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/220>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
xserver restarting with certain usb events
by Clyde E. Kunkel
In current rawhide on one of my test systems (actual hardware, not
virtual machine) when I unplug/replug the usb mouse/keyboard (they are
on a kvm switch) the xserver restarts. This started about a month ago
right after the rebuild of the X stack packages (not saying that is the
culprit, just the only timeframe I can reference).
I don't know if this is xorg-x11-drv-evdev, Xserver, systemd or what.
Any help in pinpointing would be appreciated so I can bz. Does not
occur on same machine with F16, 15 or 14.
This is a radeon HD2600 card running standard ati driver.
Xorg.0.log.old shows this activity after switching:
[ 416.790] (II) config/udev: removing device Microsoft Microsoft
Wireless Optical Mouse® 1.0A
[ 416.791] (II) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Close
[ 416.791] (II) UnloadModule: "evdev"
[ 426.712] (II) config/udev: Adding input device Microsoft Microsoft
Wireless Optical Mouse® 1.0A (/dev/input/mouse0)
[ 426.712] (II) No input driver/identifier specified (ignoring)
[ 426.713] (II) config/udev: Adding input device Microsoft Microsoft
Wireless Optical Mouse® 1.0A (/dev/input/event4)
[ 426.713] (**) Microsoft Microsoft Wireless Optical Mouse® 1.0A:
Applying InputClass "evdev pointer catchall"
[ 426.713] (II) Using input driver 'evdev' for 'Microsoft Microsoft
Wireless Optical Mouse® 1.0A'
[ 426.714] (**) Microsoft Microsoft Wireless Optical Mouse® 1.0A:
always reports core events
[ 426.714] (**) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Device: "/dev/input/event4"
[ 426.714] (--) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Vendor 0x45e Product 0x8c
[ 426.714] (--) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Found 9 mouse buttons
[ 426.714] (--) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Found scroll wheel(s)
[ 426.714] (--) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Found relative axes
[ 426.714] (--) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Found x and y relative axes
[ 426.714] (II) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Configuring as mouse
[ 426.714] (II) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Adding scrollwheel support
[ 426.714] (**) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: YAxisMapping: buttons 4 and 5
[ 426.714] (**) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: EmulateWheelButton: 4, EmulateWheelInertia: 10,
EmulateWheelTimeout: 200
[ 426.714] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.4/8-2.4:1.0/input/input7/event4"
[ 426.715] (II) XINPUT: Adding extended input device "Microsoft
Microsoft Wireless Optical Mouse® 1.0A" (type: MOUSE, id 10)
[ 426.715] (II) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: initialized for relative axes.
[ 426.715] (**) Microsoft Microsoft Wireless Optical Mouse® 1.0A:
(accel) keeping acceleration scheme 1
[ 426.715] (**) Microsoft Microsoft Wireless Optical Mouse® 1.0A:
(accel) acceleration profile 0
[ 426.715] (**) Microsoft Microsoft Wireless Optical Mouse® 1.0A:
(accel) acceleration factor: 2.000
[ 426.715] (**) Microsoft Microsoft Wireless Optical Mouse® 1.0A:
(accel) acceleration threshold: 4
[ 428.750] (II) evdev: UVC Camera (046d:0809): Close
[ 428.750] (II) UnloadModule: "evdev"
[ 428.750] (II) evdev: Microsoft Internet Keyboard Pro: Close
[ 428.750] (II) UnloadModule: "evdev"
[ 428.750] (II) evdev: Microsoft Internet Keyboard Pro: Close
[ 428.750] (II) UnloadModule: "evdev"
[ 428.750] (II) evdev: Power Button: Close
[ 428.750] (II) UnloadModule: "evdev"
[ 428.750] (II) evdev: Power Button: Close
[ 428.751] (II) UnloadModule: "evdev"
[ 428.751] (II) evdev: Microsoft Microsoft Wireless Optical Mouse®
1.0A: Close
[ 428.778] (II) UnloadModule: "evdev"
[ 428.783] Server terminated successfully (0). Closing log file.
--
Regards,
OldFart
12 years, 4 months
[Fedora QA] #154: Tracker: critical path test case creation
by fedora-badges
#154: Tracker: critical path test case creation
-------------------------+--------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
-------------------------+--------------------------------------------------
= problem =
We need more specific per-package guidance for proven tester testing, to
make sure the testing covers all the relevant critical path functionality
of each package.
= enhancement recommendation =
We can create a group of test cases in the Wiki for each critical path
package. Bodhi could integrate with this system and, in the future non-
numeric karma system, provide checkboxes for each test case for packages
which have test cases available. fedora-easy-karma could provide an
interface to display and check off test cases from the Wiki.
This ticket can serve as a tracker for this process, which will be
ongoing. To start with I will file tickets for each package which has so
far been identified (on test and devel mailing lists) as an obvious
candidate for such test cases, with a note of what should be covered for
each package. Those tickets will block this one.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/154>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #80: Add dual-boot release criteria
by fedora-badges
#80: Add dual-boot release criteria
---------------------------+------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
See [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=590661
RHBZ#590661 - GRUB bootloader should have a few seconds delay on a multi-
boot setup]
= analysis =
Due to RHBZ #590661, the dual-boot experience was not well understood and
tested for the final release. It was discovered late and unclear whether
this behavior was critical to Fedora success.
= enhancement recommendation =
The user experience of dual-boot scenarios was not well understood, as a
result RHBZ #590661 did not clearly impact the release criteria.
Recommend reviewing and making adjustments to the release criteria for
dual-boot expectations.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/80>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #93: Review options to reward key QA contributors
by fedora-badges
#93: Review options to reward key QA contributors
---------------------------+------------------------------------------------
Reporter: jlaska | Owner: jlaska
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
During Fedora 13, a small amount was available to reward several key QA
contributors for their efforts.
= analysis =
If possible, I'd like to repeat this in Fedora 14.
= enhancement recommendation =
What's the best way to say thanks?
1. Request and secure QA budget to reward key contributors
2. Researching reward options (maxamillion has discussed t-shirt ideas
with the design team)
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/93>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months