test November 2014

test@lists.fedoraproject.org

89 participants
281 discussions

[Fedora QA] #261: Revise upgrade test case set
by fedora-badges 29 Jan '15

29 Jan '15

#261: Revise upgrade test case set -----------------------------------------+---------------------------------- Reporter: adamwill | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 17 Component: Proventester Mentor Request | Version: Keywords: | -----------------------------------------+---------------------------------- Our present upgrade test cases are probably a sub-optimal set. We exercise various rarely-used choices - bootloader action, and text upgrade path - but don't exercise more common variations, like installed package sets, install media, and disk layouts. While we can't commit to supporting absolutely any upgrade, we should cover at least some _more_ cases in order to catch major fails. Based on the experience in F16 and the recommendations in the retrospective, I'd suggest we could consider dropping or downgrading the importance of some tests, perhaps: * QA:Testcase_Anaconda_Upgrade_Skip_Bootloader * QA:Testcase_Anaconda_Upgrade_Skip_Bootloader_Text_Mode * QA:Testcase_Anaconda_Upgrade_Update_Bootloader_Text_Mode and add test cases for all or some of the following scenarios (please add any other suggestions as comments): * upgrade from image written to USB stick (livecd-iso-to-disk) * upgrade with KDE (and possibly Xfce and LXDE as 'optional' test cases) * upgrade an EFI install (see also https://fedorahosted.org/fedora- qa/ticket/256 for organizational issues here) * upgrade with bootloader on first partition (not MBR) * upgrade with separate /usr , /home and /var partitions * upgrade a RAID install This should be completed ideally by Fedora 17 Alpha phase, and definitely by Beta phase (when upgrade issues become blockers). -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/261> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 13

[Fedora QA] #227: Document SOP for acceptance test event
by fedora-badges 29 Jan '15

29 Jan '15

#227: Document SOP for acceptance test event -------------------+-------------------------------------------------------- Reporter: rhe | Owner: twu Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Wiki | Version: Keywords: | -------------------+-------------------------------------------------------- So far we don't have a sop document for acceptance test events, which is needed to clarify the procedure, see other sops: * http://fedoraproject.org/wiki/Category:QA_SOPs Assign this task to twu as he's been leading this event. Feel free to take if anyone is interested in this. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/227> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 21

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

29 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 29 Jan '15

29 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 29 Jan '15

29 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 29 Jan '15

29 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 28 Jan '15

28 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

Bug 1118446 - wrong colour, instead of turquoise printing blue
by Joerg Lechner 11 Dec '14

11 Dec '14

Hi, still I can not print fotos with my Canon Pixma MP540 (F21 Final TC2, cups-gutenprint). Reason: Blue colours are printed not according to the fotos. This problem is reported and discussed in open Bug 1118446. Are there more printers showing similar problems, or is this only the problem of some Canon printers? Kind Regards

1 2

Fedora 21 Live & Xfce 4.11 x64
by poma 04 Dec '14

04 Dec '14

To share with you, Fedora 21 Live & Xfce 4.11 x64 Mousepad(ported to GTK+ 3), Parole, Alacarte, FirewallD panel applet, Firefox, Thunderbird, LibreOffice, Liberation Fonts, system-config-printer, Gutenprint, Foomatic, HP Linux Imaging and Printing Project, HP Printer Drivers, kernel 3.17.4-301, ... Includes improved xfce4*plugins and rebuilt with libxfce4ui support. Excludes xfce4*plugins dependent on libxfcegui4(deprecated). http://goo.gl/Gm4ffO Enjoy.

1 2

F21 FInal RC1 - Xfce Sensors Viewer - cannot save changes
by Robert Moskowitz 01 Dec '14

01 Dec '14

I have no experience with Xfce, let alone the panel sensors app, but it seems simple. I clicked on 'show' for one of the sensors, and nothing shows when I close the app. Further, when I go back into it, this sensor is not marked as 'show'. I also tried to change the update interval and that is not saved either. There is no 'save' button on the bottom of the dialog. Only a 'close' button.

4 7

← Newer
1
2
3
4
5
6
7
8
...
29
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 November 2014