test June 2011

test@lists.fedoraproject.org

88 participants
216 discussions

[Fedora QA] #135: Proposed Test Day - TOPIC How about a consideration of the dual boot issues from Fedora 13?
by fedora-badges 25 Feb '13

25 Feb '13

#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

2 10

[Fedora QA] #151: Tests consistent with Criterion
by fedora-badges 13 Feb '13

13 Feb '13

#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

1 26

[Fedora QA] #180: Create Package Specific Test Cases for Design Suite
by fedora-badges 03 Aug '12

03 Aug '12

#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

1 2

[Fedora QA] #82: Update existing dual-boot tests and add to test plan
by fedora-badges 08 Jun '12

08 Jun '12

#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

1 7

GNOME shell broken after suspend and resume for driver r300_dri
by Christoph Frieben 01 Apr '12

01 Apr '12

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.

3 7

[Fedora QA] #62: Description page for every test case in Package Update Acceptance Test Plan
by fedora-badges 08 Dec '11

08 Dec '11

#62: Description page for every test case in Package Update Acceptance Test Plan --------------------+------------------------------------------------------- Reporter: kparal | Owner: kparal Type: task | Status: new Priority: major | Milestone: Component: Wiki | Version: Keywords: | --------------------+------------------------------------------------------- For every test case in Package Update Acceptance Test Plan there should be a separate wiki page with detailed description what gets tested, etc. Some tools and autoqa front-ends may then reference this pages. Also it is needed for package maintainers that will surely want to read something about the test case their package has just failed. The test plan proposal referencing all the test cases is currently here: https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_acceptan… -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/62> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #205: Create test case for system logging
by fedora-badges 07 Dec '11

07 Dec '11

#205: Create test case for system logging ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | ----------------------+----------------------------------------------------- Per #151, we are missing a test case for the Alpha release criterion "A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project". We should create a test case to validate this criterion, and add it to the matrices. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/205> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 8

[Fedora QA] #204: Create test case for artwork
by fedora-badges 07 Dec '11

07 Dec '11

#204: Create test case for artwork ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | ----------------------+----------------------------------------------------- As per #151, we are missing a test case for the Alpha release criterion "The default Fedora artwork must either refer to the current Fedora release under development (Fedora 16), or reference an interim release milestone (e.g. Alpha or Beta). If a release version number is used, it must match the current Fedora release under development. This includes artwork used in the installer, firstboot, graphical boot, graphical login and desktop background." (and also for the Final criterion "The proposed final Fedora artwork must be included and enabled by default for the installer, graphical boot, firstboot, graphical login and desktop background. All Fedora artwork must be consistent with the proposed final theme, and if any artwork contains a graphical version number, the version number used must match the Fedora release number. Generic release artwork (e.g. Alpha, Beta, Development) must not be used for the final release"). We should create one or two test cases to cover these criteria and add them to the desktop matrix. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/204> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #203: Create test case for boot-to-graphical-environment
by fedora-badges 07 Dec '11

07 Dec '11

#203: Create test case for boot-to-graphical-environment ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | ----------------------+----------------------------------------------------- Per #151, we are missing an explict test case for the Alpha criterion "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied", though it is somewhat implied by the more complex desktop test cases. It would be more correct to have a specific test case for this, however. We should create one, and add it to the desktop matrix. Assigning to myself for now, but if anyone else wants to take this, please do! -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/203> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #202: Create test case for firstboot (graphic and text)
by fedora-badges 07 Dec '11

07 Dec '11

#202: Create test case for firstboot (graphic and text) ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | ----------------------+----------------------------------------------------- Per #151, we are missing test cases for firstboot functionality, which is required by Alpha release criterion "In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account". We should create a test case to verify this requirement and add it to the matrices. Assigning to myself for now, but anyone else, feel free to jump in! -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/202> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

3 7

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test June 2011