test June 2014

test@lists.fedoraproject.org

49 participants
177 discussions

[Fedora QA] #273: Improve browseability of validation matrix pages
by fedora-badges 30 Jan '15

30 Jan '15

#273: Improve browseability of validation matrix pages -----------------------------------------+------------------------ Reporter: adamwill | Owner: adamwill Type: enhancement | Status: new Priority: major | Milestone: Fedora 17 Component: Proventester Mentor Request | Version: Keywords: | Blocked By: Blocking: | -----------------------------------------+------------------------ = problem = cwickert and sandro have told us they have trouble finding the validation matrix pages when they need them. = analysis = we do have the pages logically named and categorized, but it's still not that easy to, for e.g., see all the desktop result pages for a given release at a glance. = enhancement recommendation = We could add more categories, for example "Fedora XX {{desktop,base,install}} validation results" categories, and any others that come to mind (suggestions please!) It would be nice to have 'next / previous' links that would let you browse from Final RC4 back to Final RC3 back to Final RC2 back to Final RC1 back to Final TC2 back to Final TC1 back to Beta RC4 and so on, but I'm not sure if that's plausible to implement automatically (it would be relatively easy to do manually when creating the pages, though). -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/273> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

[Fedora QA] #228: SOPs for Everything
by fedora-badges 30 Jan '15

30 Jan '15

#228: SOPs for Everything ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 17 Component: Wiki | Version: Keywords: | ----------------------+----------------------------------------------------- We should have...SOPs for Everything! This is a meta-ticket with the aim of identifying, well, everything QA does, and making sure they all have SOPs. For a start, I'm going to do a survey of the QA calendar for a release, and check whether we have an SOP for each task. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/228> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

[Fedora QA] #449: Proposed Test Day - Cockpit
by fedora-badges 30 Jan '15

30 Jan '15

#449: Proposed Test Day - Cockpit ----------------------+------------------------ Reporter: stefw | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ Ownership: Stef Walter <stefw(a)redhat.com>, Marius Vollmer <mvollmer(a)redhat.com> Time frame: Would like a test day allocated late in the test cycle. Features: https://fedoraproject.org/wiki/Changes/CockpitManagementConsole -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/449> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 10

[Fedora QA] #448: Proposed Test Day - Virtualization
by fedora-badges 30 Jan '15

30 Jan '15

#448: Proposed Test Day - Virtualization ----------------------+------------------------ Reporter: crobinso | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I'd like to propose a test day for Virtualization. Preferred date would be mid to late August. We will be doing general virt testing, like the standard test cases we carry over for each test day: http://fedoraproject.org/wiki/Test_Day:2013-10-08_Virtualization And likely some specific test cases for our f21 feature: https://fedoraproject.org/wiki/Changes/Virt_64bit_ARM_on_x86 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/448> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 13

[Fedora QA] #447: Proposed Test Day - ARM
by fedora-badges 30 Jan '15

30 Jan '15

#447: Proposed Test Day - ARM ----------------------+-------------------------- Reporter: pwhalen | Owner: Paul Whalen Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+-------------------------- = phenomenon = Proposed test day for ARM to occur between Alpha and Beta. = implementation recommendation = Testing to include all deliverables and target platforms (including Allwinner sunxi ARM SoC support). -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/447> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #446: Proposed Test Day - NetworkManager
by fedora-badges 30 Jan '15

30 Jan '15

#446: Proposed Test Day - NetworkManager ----------------------+------------------------ Reporter: vbenes | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I would like to schedule a test day for NetworkManager. Anytime between Alpha and Beta -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/446> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

[Fedora QA] #444: Proposed Test Day - GNOME-3.14
by fedora-badges 30 Jan '15

30 Jan '15

#444: Proposed Test Day - GNOME-3.14 ----------------------+------------------------ Reporter: vbenes | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 21 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ Hi, would like to schedule a test day for GNOME-3.14.. somewhere between alpha and beta -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/444> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

[Fedora QA] #441: Sysadmin permission to beaker for desktop qe
by fedora-badges 30 Jan '15

30 Jan '15

#441: Sysadmin permission to beaker for desktop qe -------------------------+------------------ Reporter: vrutkovs | Owner: Type: task | Status: new Priority: major | Milestone: Component: permissions | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------ Please add vrutkovs, vhumpa and vbenes to beaker's sysadmin group in order to work on desktop tests for Fedora. Approved by tflink -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/441> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #429: temporary membership in sysadmin-qa for atodorov so that beaker trial can continue
by fedora-badges 30 Jan '15

30 Jan '15

#429: temporary membership in sysadmin-qa for atodorov so that beaker trial can continue -------------------------+------------------ Reporter: tflink | Owner: Type: task | Status: new Priority: minor | Milestone: Component: permissions | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------ = phenomenon = Long story short, atodorov is helping with the beaker trial we're doing and he needs shell access to the machine in order to complete his work. Assuming that this trial is successful, access to the beaker system(s) will be controlled with a separate FAS group but until that is set up, sysadmin-qa membership is the only way to get the required access. I don't expect the need for membership to last any more than a couple of weeks. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/429> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #404: Look through validation matrices and note which tests don't apply to ARM
by fedora-badges 30 Jan '15

30 Jan '15

#404: Look through validation matrices and note which tests don't apply to ARM ----------------------+------------------------ Reporter: adamwill | Owner: pwhalen Type: task | Status: new Priority: blocker | Milestone: Fedora 20 Component: Wiki | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ In the effort to revise the validation pages for ARM, it would help a lot to know which test cases in the existing set are not sensibly applicable to ARM validation. If an ARM folk could go through the pages and list which cases do not apply, that'd be great. Please refer to: * https://fedoraproject.org/wiki/QA:Fedora_20_Install_Results_Template * https://fedoraproject.org/wiki/QA:Base_validation_results_template * https://fedoraproject.org/wiki/QA:Desktop_validation_results_template Thanks! -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/404> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 5

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 2014