test July 2010

test@lists.fedoraproject.org

84 participants
222 discussions

[Fedora QA] #90: Make blocker bug nag mails part of the SOP
by fedora-badges 25 Nov '10

25 Nov '10

#90: Make blocker bug nag mails part of the SOP ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: poelstra Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = We have a lot of bugs, and the deadlines for resolving bugs (where resolving == [fixing, documenting]) is not always clear. = analysis = During the lead up to F-13-RC, numerous reminder emails were sent to test@ and devel@ mailing lists noting the number and state of remaining blocker bugs. It is felt that, along with developer time of course, the attention to the blocker list contributed to the resolution of 67 blocker bugs from 2010-04-30 to 2010-05-06. Not knowing which bugs were already reviewed, also introduced time wasted reviewing previously reviewed bugs during blocker review meetings. = enhancement recommendation = 1. Recommend more frequent blocker status emails leading up to '''each''' major milestone. Unclear who should be responsible for sending these mails, QA, rel-eng or program mgmt? 2. Update [https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting QA:SOP_Blocker_Bug_Meeting] with blocker meeting queries or ''python- bugzilla'' commands and where to send the mails (developers bcc'd?) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/90> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #85: Clarify wiki test priority
by fedora-badges 25 Nov '10

25 Nov '10

#85: Clarify wiki test priority ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = There was some confusing around the priority listed in the install and desktop test matrices. The question was, why do we give the ''go'' decision to release, even when there are test failures from tests with a matching release level? = analysis = Adam pointed out that ''this is because the bugs exposed caused the test to 'fail', but don't really break the underlying release criteria. I think we could perhaps track this type of 'failure' specifically in the results tables).'' = enhancement recommendation = I ''think'' this is a messaging/education issue. Perhaps we just need to clarify that the priority listed is the test execution priority. It does not always mean that a failure identified by those tests will block the applicable release. Updates or adjustments may be needed to the https://fedoraproject.org/wiki/QA/SOP_Release_Validation_Test_Event or to the Fedora 14 test results template (when available -- https://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/85> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #108: Proposed Test Day - Sugar on a Stick
by fedora-badges 25 Nov '10

25 Nov '10

#108: Proposed Test Day - Sugar on a Stick ----------------------+----------------------------------------------------- Reporter: sdz | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 14 Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- Ownership - It'd probably be good if we had both somebody from the SoaS team (at the very least I can sign up, maybe also Mel and Peter) and Fedora QA hosting this. Time frame - August 19 would be our favorite pick. Feature - http://fedoraproject.org/wiki/Features/Sugar_0.90 Spin - http://fedoraproject.org/wiki/Sugar_on_a_Stick Notes - http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_proce… -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/108> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #109: Proventester Mentor Request (fcami)
by fedora-badges 17 Nov '10

17 Nov '10

#109: Proventester Mentor Request (fcami) -----------------------------------------+---------------------------------- Reporter: fcami | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- I would like to request a mentor to become Proventester. I have read http://fedoraproject.org/wiki/Proven_tester, I agree to abide by the testing requirements and I know how to use bodhi and bugzilla. I do triage from time to time (mainly xorg, especially xorg-x11-drv-ati and mesa). I already use updates-testing enabled for quite of bit of my packages, including some in the critical path, on about five different workstations and servers -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/109> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 9

[Fedora QA] #87: Expand desktop release criteria and validation
by fedora-badges 07 Oct '10

07 Oct '10

#87: Expand desktop release criteria and validation ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: adamwill Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = [http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Desktop test results] were often not available for non-GNOME desktops. This leaves a large exposure come release day (for Alpha, Beta or Final). = analysis = The desktop release criteria are specific to GNOME. As a result, there is no incentive to finding bugs in XFCE, LXDE or KDE. = enhancement recommendation = This might be too much for once ticket. Feel free to split this out into more if needed. Recommend looking for opportunities to improve communication between teams and increasing non-GNOME desktop testing leading up to milestones. * The goal is to extend the desktop validation testing introduced in Fedora 13 to cover the main non-default desktops: KDE, Xfce and LXDE. * Update appropriate desktop validation content as needed (see [http://fedoraproject.org/wiki/QA:Desktop_validation_testing desktop validation testing]) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/87> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #94: Add several release criteria based on feedback from desktop SIGs
by fedora-badges 07 Oct '10

07 Oct '10

#94: Add several release criteria based on feedback from desktop SIGs -----------------------------------------+---------------------------------- Reporter: adamwill | Owner: adamwill Type: defect | Status: new Priority: major | Milestone: Fedora 14 Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- Discussing the expansion of desktop validation testing to other major desktops - https://fedorahosted.org/fedora-qa/ticket/87 - has resulted in several proposed additional release criteria: * Saving passwords in the desktop default keyring (if the desktop implements one), and retrieving passwords from the keyring, must work * The desktop default update manager must not periodically check for updates when the system is booted live, but must periodically check for updates when running on an installed system * The desktop's offered mechanisms for shutting down, logging out and rebooting must work We should consider adding these to the release criteria, and select appropriate levels for each. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/94> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #105: F14 Graphics Test Week
by fedora-badges 07 Oct '10

07 Oct '10

#105: F14 Graphics Test Week ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: defect | Status: new Priority: major | Milestone: Fedora 14 Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- We should have a Graphics Test Week for F14, as usual. I will organize it. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/105> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #104: F14 systemd Test Day
by fedora-badges 07 Oct '10

07 Oct '10

#104: F14 systemd Test Day ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: defect | Status: new Priority: major | Milestone: Fedora 14 Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- Lennart is enthusiastic about having a Test Day for systemd for F14. I will organize one. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/104> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 7

[Fedora QA] #92: Define proventester process
by fedora-badges 29 Sep '10

29 Sep '10

#92: Define proventester process ---------------------------+------------------------------------------------ Reporter: jlaska | Owner: Type: enhancement | Status: new Priority: major | Milestone: Fedora 14 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = During Fedora 13, karma from members of the FAS 'qa' group was required for critical path package updates. We don't have a clear process for joining and contributing to this effort. = analysis = Not much else to say here. We have critical path packages that need testing. = enhancement recommendation = Some of this is already complete, or inprogress (thanks dafrito, maxamillion and adamw) 1. document how people can join - https://fedoraproject.org/wiki/QA/JoinProvenTesters 2. document what is expected of members - https://fedoraproject.org/wiki/Proven_tester 3. What else? -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/92> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #112: 'Translation/Keyboard in anaconda' Test Day - 2010/09/09
by fedora-badges 21 Sep '10

21 Sep '10

#112: 'Translation/Keyboard in anaconda' Test Day - 2010/09/09 ----------------------+----------------------------------------------------- Reporter: rhe | Owner: rhe Type: task | Status: new Priority: major | Milestone: Fedora 14 Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- As talked with Igor in test list, this test day will be held on 2010/09/09, this ticket is used to track this event.[[BR]] So far, we have [https://fedoraproject.org/wiki/Category:I18n_Installation Category:I18n_Installation] as test cases for this test day. But these tests need be modified, and maybe new tests will be added to have a better coverage for testing. [[BR]] Please mark this day in your calender, and help gathering participation by announcing it both inside and outside the teams when it's coming. [[BR]] If you have any concern, feel free to reply directly in this ticket. [[BR]] [[BR]] Many thanks,[[BR]] Hurry -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/112> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 23

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test July 2010