[Fedora QA] #135: Proposed Test Day - TOPIC How about a consideration of the dual boot issues from Fedora 13?
by fedora-badges
#135: Proposed Test Day - TOPIC How about a consideration of the dual boot
issues from Fedora 13?
-----------------------+----------------------------------------------------
Reporter: dramsey | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Day | Version:
Keywords: dual boot |
-----------------------+----------------------------------------------------
How about a consideration of the dual boot issues from Fedora 13?
I remember from the Fedora 13 timeframe, there were dual boot issues.
Would it be advantageous to reconsider a subset of this as well as other
lessons learned from the Fedora 13 which may be a good peruse for
historical impact and reflection.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/135>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 1 month
[Fedora QA] #151: Tests consistent with Criterion
by fedora-badges
#151: Tests consistent with Criterion
---------------------------+------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 15
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
Criteria was kept changing during F-14 test cycle, but some installation
tests didn't update accordingly. On the other hand, the criterion should
be modified to include preupgrade_from_older_release test and new tests
created for F-15.
= enhancement recommendation =
Installation tests need be reviewed and updated to fit for the criterion.
Criterion for preupgrade_from_older_release test is required.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/151>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
11 years, 2 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, 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, 10 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.
12 years
[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