test August 2011

test@lists.fedoraproject.org

117 participants
334 discussions

[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

[Fedora QA] #192: Proposed Test Day - IPv6 - June 8, 2011 (Wednesday)
by fedora-badges 07 Dec '11

07 Dec '11

#192: Proposed Test Day - IPv6 - June 8, 2011 (Wednesday) ----------------------+----------------------------------------------------- Reporter: lwang | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 15 Component: Test Day | Version: Keywords: IPv6 | ----------------------+----------------------------------------------------- On Jun 8, 2011 - the World IPv6 Test Day, we like to host a fedora IPv6 test day as well to help our fedora users to test out Fedora15's readiness on IPv6. A description of the World IPv6 Day is here: http://isoc.org/wp/worldipv6day/ And the full fedora IPv6 Test Day project is described here: https://fedoraproject.org/wiki/QA/Test_Day:2011-06-08_IPv6 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/192> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 13

[Fedora QA] #179: Proposed Test Day - general bootloader and dual-boot event
by fedora-badges 07 Dec '11

07 Dec '11

#179: Proposed Test Day - general bootloader and dual-boot event ----------------------+----------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- Dlehman informed me of tentative plans to transition to grub2 in Fedora 16. Documentation and development hasn't finished yet, so things are still somewhat flexible. This ticket serves as a mental-note so we don't forget this when Fedora 16 test day planning starts. https://fedoraproject.org/wiki/Anaconda/Features/Grub2Migration -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/179> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #219: Create virtualization installation validation test cases
by fedora-badges 07 Dec '11

07 Dec '11

#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

1 6

[Fedora QA] #198: Clarifying ways to verify updated and skipped bootloader
by fedora-badges 07 Dec '11

07 Dec '11

#198: Clarifying ways to verify updated and skipped bootloader -------------------------+-------------------------------------------------- Reporter: rhe | Owner: rhe Type: enhancement | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | -------------------------+-------------------------------------------------- The installation matrix now contains the update bootloader and skip bootloader tests which need be updated to better detect whether the bootloader was skipped or updated. (This ticket is branched from [https://fedorahosted.org/fedora-qa/ticket/86 ticket#86]) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/198> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #230: QA:Testcase_Anaconda_autopart_(encrypted)_install overlaps with QA:Testcase_base_startup
by fedora-badges 07 Dec '11

07 Dec '11

#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

1 1

[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 07 Dec '11

07 Dec '11

#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

1 2

[Fedora QA] #154: Tracker: critical path test case creation
by fedora-badges 07 Dec '11

07 Dec '11

#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

3 57

← Newer
1
2
3
4
5
6
7
...
34
Older →

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 August 2011