[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, 8 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, 8 months
[Fedora QA] #82: Update existing dual-boot tests and add to test plan
by fedora-badges
#82: Update existing dual-boot tests and add to test plan
---------------------------+------------------------------------------------
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 =
Recommend updating existing dual-boot test cases, and create new test as
needed, to reflect updated dual-boot release criteria. Also, add tests to
the install matrix (depends on ticket#80).
The current tests concern dual-booting windows and Mac. I believe Mac is
no longer a primary concern. However, we may wish to add a test for dual-
booting Ubuntu or even Fedora.
See existing dual-boot tests at
https://fedoraproject.org/wiki/Category:Installer_Dual_Boot_Test_Cases
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/82>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 9 months
[Fedora QA] #259: Review Fedora 17 feature list and co-ordinate with owners of significant features to create test plans
by fedora-badges
#259: Review Fedora 17 feature list and co-ordinate with owners of significant
features to create test plans
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: critical | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
We should have someone responsible for reviewing the Fedora 17 feature
list and ensuring a good test plan is in place for any significant and
potentially disruptive feature. This ticket is for the general process of
reviewing the entire feature list; whoever does this may well choose to
create separate tickets for the test plans for specific features.
If you're interested in working on this, please feel free to assign the
ticket to yourself.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/259>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 9 months
[Fedora QA] #256: Add EFI data to installation / base results matrices
by fedora-badges
#256: Add EFI data to installation / base results matrices
-------------------------------+--------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: critical | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: efi retrospective |
-------------------------------+--------------------------------------------
It would be nice if we could explicitly include EFI install test results
in the installation matrix.
Right now we just have the efidisk.img test case, which is kind of
outdated: we don't just have a 'special' EFI boot disk any more, EFI
support is integrated into all images.
I'm not yet sure of the best way to lay this out, but I think we need to
capture:
* result of a straight-through DVD install booted via EFI
* result of a straight-through live CD install booted via EFI
* result of a straight-through live-image-written-to-USB-by-livecd-iso-to-
disk install booted via EFI
* result of a straight-through DVD-image-written-to-USB-by-l-i-t-d install
booted via EFI
* result of preupgrading an EFI install
* result of DVD upgrading an EFI install
I think other test cases don't necessarily need to be done both BIOS and
EFI, but we probably need at least the above results.
One way to do this would be to add an "EFI" column to the installation and
base results matrices, and only provide boxes in that column for the test
cases that cover the above features. But that's just one idea; there may
be a better way.
This should be completed in time for F17 Alpha, as EFI boot is considered
Alpha-critical for F17.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/256>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 9 months
[Fedora QA] #260: Cover USB-written images better in installation validation testing
by fedora-badges
#260: Cover USB-written images better in installation validation testing
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
It became clear in the Fedora 16 cycle that use of Fedora images (both
live and non-live) written to USB sticks is now extensive, and our current
installation validation tests don't really test this method very
comprehensively. We should extend the installation validation matrix to
cover at least boot and installation in the following situations:
* Live image written to USB stick using livecd-iso-to-disk
* Live image written to USB stick using liveusb-creator
* Live image written to USB stick using dd
* Non-live image written to USB stick using livecd-iso-to-disk
* Non-live image written to USB stick using dd
We may want to consider different l-i-t-d parameters also (especially the
use or non-use of --format could be significant). We could also cover use
of unetbootin as an _informational_ (non-blocking) test, but I'm not super
sure about that.
Part of this ticket is deciding on the best way to represent this -
whether it's by simply creating new test cases and adding them into the
matrix, or somehow re-rendering the matrix to cover these cases as
'variants' of existing test cases, or some other method.
The changes from this ticket and https://fedorahosted.org/fedora-
qa/ticket/256 should be co-ordinated (possibly handled by the same person
or group) as they both involve similar questions of how to revise the
matrix to cover more situations.
This should be completed by Fedora 17 Alpha TC1.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/260>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 9 months
GNOME shell broken after suspend and resume for driver r300_dri
by Christoph Frieben
Can anybody report success for the suspend and resume cycle triggered
from within the GNOME shell when the graphics card is based on some
R300/R400 variant? In my case, the shell is still broken after resume.
The video device is some ATI Radeon X800 card which is using the R420
chip. Only a black desktop, a mouse pointer and the GNOME panel are
visible after resume. The desktop is not completely frozen since I am
still able to move the mouse pointer. It is also possible to switch to
a VT in order to reboot the system. Thanks, ~C
PS: The F15 development cycle is nearing completion, and in my
opinion, this is a major usability issue.
11 years, 12 months
F16 Alpha GRUB install failure
by Michael Schwendt
Between TC1 and release of F16 Alpha, something must have changed to the
worse with regard to installing GRUB to a partition's primary sector.
Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3.
Anaconda now reports failure to install, and I've found this on virtual
console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a
partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be
installed in this setup using blocklists. However, blocklists are
UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
12 years, 1 month
[Fedora QA] #258: Create EC2 test cases and integrate into validation matrices
by fedora-badges
#258: Create EC2 test cases and integrate into validation matrices
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: tflink
Type: task | Status: new
Priority: critical | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
tflink highlighted the need for better EC2 testing in the F16 QA
retrospective. We should create test cases for install (or direct
deployment via image) of Fedora onto EC2 and validating basic
functionality. This might go into the Base matrix rather than the
installation matrix.
Assigning to tflink and dgilmore as they're the most plugged into EC2, it
seems.
Should be complete ideally by F17 Alpha TC1, definitely by Final TC1.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/258>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 2 months
[Fedora QA] #257: Create and maintain F17 install test plan
by fedora-badges
#257: Create and maintain F17 install test plan
-----------------------------------------+----------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
We need an installation test plan for Fedora 17, can be modelled on
previous ones:
* https://fedoraproject.org/wiki/QA:Fedora_16_Install_Test_Plan
* https://fedoraproject.org/wiki/QA:Fedora_15_Install_Test_Plan
etc. Note that some of the copypasta on that page dates back to well
before the current matrices and blocker process were in operation and
could probably be revised.
The main benefit of the test plan should be to plan for major changes to
the installation process caused by F17 features. The anaconda UI rewrite
is an obvious one, but there may be others. For F16, for instance, we
could have used this document to better handle the grub2 and GPT changes.
So for F17 we should take advantage of the opportunity.
This needs to be in place ahead of F17 Alpha TC1.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/257>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 2 months