[Fedora QA] #284: Create advisory installation validation test cases for VirtualBox
by fedora-badges
#284: Create advisory installation validation test cases for VirtualBox
----------------------+------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
Although kernel team (and the rest of the development team) specifically
don't want to commit to supporting VirtualBox, the practical fact is that
a lot of people like to run Fedora in VirtualBox, and we don't at present
have formal testing in place to find out if it's actually working during
release validation.
In practice, we usually find out about any bugs via people trying it and
then posting their results to test@ or the forums, but this is pretty
rough and ready and it's easy to lose the information. If we add formal
VBox testing to the release validation process we'll probably find out
about VBox fails sooner and do a better job of tracking them for possible
fixes or at least documentation at release time.
So, ideally, we should write test cases for deploying Fedora as a VBox
guest (and possibly using it as a VBox host), and add these to the
installation validation matrix as 'advisory' tests (tests not associated
with Alpha, Beta or Final release phases, and without a corresponding
release criterion).
Dan Mashal, who I hope I've added to CC, is interested in this topic and
may choose to be an awesome rock star and contribute the test cases :)
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/284>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 7 months
[Fedora QA] #180: Create Package Specific Test Cases for Design Suite
by fedora-badges
#180: Create Package Specific Test Cases for Design Suite
---------------------------------------------+------------------------------
Reporter: sdz | Owner:
Type: task | Status: new
Priority: minor | Milestone: Fedora 15
Component: Wiki | Version:
Keywords: design suite, package test plan |
---------------------------------------------+------------------------------
The Design Suite has been promoted at SXSW and other conferences. We want
to make sure that the included applications are all working and in a good
state. Adam introduced package specific test cases at FUDCon in Tempe. We
should consider creating test cases for the most important tools, such as
blender, gimp, inkscape and shotwell.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/180>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 7 months
[Fedora QA] #287: Add Bodhi testing guidelines to Bodhi?
by fedora-badges
#287: Add Bodhi testing guidelines to Bodhi?
-------------------------+------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------
My thinking process:
1. I was about to test
https://admin.fedoraproject.org/updates/NetworkManager-0.9.3.997-0.7.fc17
2. I realized I don't know what karma to post when NM works in general,
but I haven't tested the linked bug fixes
3. I know we have some karma guidelines somewhere on the wiki
4. I couldn't find the page
5. I found the page at
https://fedoraproject.org/wiki/Proven_tester#Feedback_procedures after
some time
6. My use case doesn't seem to be mentioned anyway. But that's not
important. The question is - shouldn't we link these instructions directly
from the bodhi page? No one will find it otherwise.
That wiki page is proven tester specific, but the "Feedback procedures"
chapter is not. I think it would be really worth the effort to create a
new wiki page containing just guidelines for correct karma posting and
then ask Bodhi maintainers to link that page directly from the Bodhi page.
I imagine it could be displayed besides the "Add a comment" text are,
named something like "Karma posting guidelines".
What do you think?
Does anyone feel like volunteering for creating this separate wiki page?
I'll gladly create a ticket for Bodhi afterwards.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/287>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 7 months
[Fedora QA] #235: request: add tests for new grub2 stage2 device types
by fedora-badges
#235: request: add tests for new grub2 stage2 device types
-----------------------------------------+----------------------------------
Reporter: dlehman | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
= phenomenon =
GRUB2 supports several new md raid levels (0,4,5,6,10) and also lvm
logical volumes as the /boot device. It would be nice to get some testing
coverage for this, including combinations like root on lvm (no separate
/boot) w/ md raid pvs.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/235>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 7 months
[Fedora QA] #280: Request for F17 firewalld test day on 2012-03-15
by fedora-badges
#280: Request for F17 firewalld test day on 2012-03-15
-----------------------------------------+------------------
Reporter: twoerner | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------
I'd like to run a firewalld test day on 2012-03-15. firewalld is the new
firewall solution in Fedora with network zones support.
The tests should cover interaction with NetworkManager, libvirt and
printer configuration/discovery. Maybe more tests are possible for other
projects.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/280>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 8 months
Re: nfs-idmap.service removed
by Ed Greshko
On 04/26/2012 11:40 PM, Steve Dickson wrote:
> There was support added to the F17 kernel as well as the F17 nfs-utils,
> namely the nfsidmap command which replaces the need for the
> rpc.idmapd daemon.
Thanks....
11 years, 9 months
F17: gedit: drag & drop freezes forever mouse pointer on drag mode
by Pedro Francisco
I need to confirm a bug.
Open one gedit window (MUST BE FROM GNOME-SHELL, either from ALT+F2
and 'gedit' or using the gnome-shell menus).
On a command line do, for example:
$ gedit ~/.bashrc
_Another_ gedit window should open.
To allow you to resume your work afterwards, on another console, do:
$ sleep 15; killall gedit
Try to drag and drop the ".bashrc" tab to the other gedit window.
Watch your mouse pointer freeze on drag mode, disabling it
effectively; keyboard does not seem to respond as well. After ~15
seconds, when gedit windows are killed, you'll get your mouse and
keyboard back.
Can anyone confirm?
--
Pedro
11 years, 9 months