test November 2011

test@lists.fedoraproject.org

95 participants
278 discussions

[Fedora QA] #221: Reduce Blocker Bug Review Meeting Length
by fedora-badges 28 Jan '15

28 Jan '15

#221: Reduce Blocker Bug Review Meeting Length -------------------------+-------------------------------------------------- Reporter: tflink | Owner: Type: enhancement | Status: new Priority: major | Milestone: Fedora 16 Component: Trac | Version: Keywords: | -------------------------+-------------------------------------------------- == Description == While the [https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting blocker bug review meetings] are very much a necessary thing, they have a tendency to be long, tedious and not a whole lot of fun for those involved. During the Fedora 15 retrospective, there was a request to streamline the process in order to distribute the workload and avoid more 4+ hour meetings. Any proposals on how to reduce the length of the meetings while maintaining their utility would be much appreciated. == Proposals == Pending discussion in comments and email -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/221> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 15

[Fedora QA] #152: Test Cases Management
by fedora-badges 28 Jan '15

28 Jan '15

#152: Test Cases Management ---------------------------+------------------------------------------------ Reporter: rhe | Owner: rhe Type: enhancement | Status: new Priority: major | Milestone: Fedora 15 Component: Wiki | Version: Keywords: retrospective | ---------------------------+------------------------------------------------ = problem = We've been using mediawiki to manage tests and record results, though it's easy to approach, it has limitations such as managing, tracking and querying cases+results. So is it time for us to consider another solution such as TCMS? = analysis = Here I quoted the suggestion from Victer Chen: some advantages of TCMS: * Better to record, track and query test results, * Allow user focus on test contents instead of document maintenance. * Share test cases However, it couldn't be flexible as wiki. I think the most important things need balance are below: - Barriers Fedora should provide very low barriers. TCMS could be configured to allow anonymous user login and limit it's permission. Also, we can consider using fedora account to login TCMS. - Safety Wiki provides the ability to rollback content easily, while TCMS couldn't. What TCMS can do is recording all the history and allow user recovery it manually. But if we configure the permission well, it should not be a big problem. = enhancement recommendation = Work with TCMS team and package it to Fedora. Set up the system and use it in a small scale first. If it turns out good, enlarger the scale. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/152> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

4 25

[Fedora QA] #81: Add i18n release criteria
by fedora-badges 28 Jan '15

28 Jan '15

#81: Add i18n 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=571900 RHBZ#571900 - Keyboard mapping not correct (USA instead of Belgium) when first login after install Fedora 13 Alpha] = analysis = * Currently we don't have i18n installation cases, so local language install is not tested as a demand. Untranslated pages are still existing after RC test. Such cases needed be added in test as well as release criteria. * Does the Fedora i18n team have any release criteria to propose? * RHBZ #571900 pointed out the need for a better understanding of how the language and keymap installer selections impact the installed system. = enhancement recommendation = Recommend reviewing the release criteria to ensure expectations are captured around propagating language and keymap settings from install to desktop login (/etc/sysconfig/i18n, image:Package-x-generic-16.pnggdm etc...). It may also be advised to coordinate with the installer team so that bugs can be filed for any missing functionality. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/81> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 8

[Fedora QA] #61: make VirtioSerial Test cases clearer
by fedora-badges 28 Jan '15

28 Jan '15

#61: make VirtioSerial Test cases clearer ----------------------+----------------------------------------------------- Reporter: liam | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- we have VirtioSerial Test cases here: https://fedoraproject.org/wiki/Test_Day:2010-04-08_Virtualization_VirtioSer… but during test day, none of these cases was executed. I think testers did not know how to run these cases, so Amit, could you like to rewrite these cases with template and make it clearer? The good cases can help make VirtioSerial better and better,it also can involve more fedora people in virtio.Thanks in advance. These cases that are written with template for your reference: https://fedoraproject.org/wiki/QA:Fedora_13_Install_Results_Template#Test_M… Or if you don't know how to use template, just write the test step more specific and send the cases to me, I will convert them to standard format. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/61> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

[Fedora QA] #46: Write Test cases for LXDE components.
by fedora-badges 27 Jan '15

27 Jan '15

#46: Write Test cases for LXDE components. ----------------------+----------------------------------------------------- Reporter: johannbg | Owner: johannbg Type: task | Status: new Priority: major | Milestone: Component: Test Day | Version: Keywords: | ----------------------+----------------------------------------------------- An ticket to keep track on LXDE components that need test cases and how to debug pages * PCManFM: File manager, provides desktop icons * LXPanel: Feature-rich desktop panel * LXSession: Standard-compliant X11 session manager with shutdown/reboot/suspend support via HAL ( FEI https://fedoraproject.org/wiki/Features/HalRemoval ) * LXSession-edit: GUI to configure what’s automatically started in LXDE * lxde-settings-daemon: XSettings Daemon * LXInput: Keyboard and mouse settings dialog * LXRandR: Configuration tool for monitors and external projectors * LXAppearance: Feature-rich GTK+ theme switcher able to change GTK+ themes, icon themes, and fonts * LXTask: Lightweight task manager derived from xfce4 task manager * LXTerminal: Desktop-independent VTE-based terminal emulator * LXLauncher: Open source replacement for the Asus Launcher on the EeePC * LXShortcut: Small utility to edit application shortcuts, used by lxpanel and lxlauncher * LXNM (still under development): Lightweight network manager for LXDE supporting wireless connections (not yet in Fedora ) * LXRandR (still under development): Monitor configuring tool * Openbox: Lightweight, standard-compliant, and highly-configurable window manager. * GPicView: A very simple, fast, and lightweight image viewer featuring immediate startup * Leafpad: Lightweight and simple text editor * XArchiver: Lightweight, fast, and desktop-independent gtk+-based file archiver * LXDM: Display manager -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/46> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 7

[Fedora QA] #229: asking to join the proven testers and requesting a mentor
by fedora-badges 18 Dec '13

18 Dec '13

#229: asking to join the proven testers and requesting a mentor -----------------------------------------+---------------------------------- Reporter: appelond | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- = phenomenon = = reason = I would like to help getting stuff approved for the Fedora Repos. = recommendation = -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/229> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #254: proventester request
by fedora-badges 18 Dec '13

18 Dec '13

#254: proventester request -----------------------------------------+---------------------------------- Reporter: piyushsaini | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- Hi, I want to join the proven testers and its a humble request to ADMIN please assign me a mentor. Thanks & Regards, Piyush Saini -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/254> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #249: Proventester mentor request
by fedora-badges 18 Dec '13

18 Dec '13

#249: Proventester mentor request -----------------------------------------+---------------------------------- Reporter: kaushikub | Owner: Type: proventester request | Status: new Priority: major | Milestone: Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- = phenomenon = 6 years of testing experience = reason = I have been testing SSSD for almost a year. Thanks, Kaushik https://fedoraproject.org/wiki/User:Kaushikub -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/249> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[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

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