test March 2014

test@lists.fedoraproject.org

39 participants
165 discussions

[Fedora QA] #424: Proposed Test Day - KDE 4.11
by fedora-badges 11 Aug '14

11 Aug '14

#424: Proposed Test Day - KDE 4.11 ----------------------+------------------------ Reporter: mbriza | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ = phenomenon = KDE Plasma Workspaces test day for Fedora 20 Proposed date is 7th November, 2013. = implementation recommendation = We, as the KDE SIG need to test our three proposed features: * KDE Plasma Workspaces 4.11 * Plasma-nm * SDDM as the default KDE display manager instead of KDM as well as the regular KDE tests ran before every Fedora release -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/424> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #420: Power management testday
by fedora-badges 11 Aug '14

11 Aug '14

#420: Power management testday ----------------------+------------------------ Reporter: jskarvad | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ We would like to run Power management test day. The arrangement will be similar to our previous Power management test days. We can prepare the live medium ourselves. We propose 2013-11-14, but any other date should fit. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/420> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #409: Fedora 20 i18n Test Day
by fedora-badges 11 Aug '14

11 Aug '14

#409: Fedora 20 i18n Test Day ----------------------+------------------------ Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ I18N (Internationalization) Test Day Test Date: TBD Fedora 20 Schedule: http://fedoraproject.org/wiki/Releases/20/Schedule Required: Live ISO, it may not be same as l10n test day. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/409> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 10

[Fedora QA] #408: Fedora 20 Translation Test Day
by fedora-badges 11 Aug '14

11 Aug '14

#408: Fedora 20 Translation Test Day ----------------------+------------------------ Reporter: aalam | Owner: Type: task | Status: new Priority: major | Milestone: Fedora 20 Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------------ = phenomenon = Translation Test day for Fedora 20. Test Date: need to decide. It is before 'Software Translation Freeze' (2013-10-08). proposed date: Thursday Sep 26 (2013-09-26) = implementation recommendation = - need to review test cases for gnome-3.10 - need to create test for Anaconda fltg team will help for that. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/408> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 9

[Fedora QA] #407: Bluetooth Test Day
by fedora-badges 11 Aug '14

11 Aug '14

#407: Bluetooth Test Day ----------------------+------------------ Reporter: martix | Owner: Type: task | Status: new Priority: major | Milestone: Component: Test Day | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------ I'd like to do Bluetooh Test Day on 2013-10-17 Change: http://fedoraproject.org/wiki/Changes/Bluez5 -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/407> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

slow mirror workaround?
by Felix Miata 24 Apr '14

24 Apr '14

Trying to yum upgrade 19 is stuck on a mirror with no useful throughput. What kind of workaround for this is available? Nothing jumps at me in the yum man page. How do I specify to use a particular mirror know to work? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

6 8

yum install @kde-desktop not working?
by Pedro Francisco 08 Apr '14

08 Apr '14

Hello! I may in the past hit CTRL+C a few times during yum operation but since I did a RPM database rebuild I was expecting it would not be the cause of my issue. That being said, I'm having issues after a system cleanup. I did # yum remove qt* kdelibs* gtk* and now when I do: # yum install kdm; yum install @kde-desktop it would seem some dependencies are not installed (not even the option to start KDE appears on KDM). ( I also tried # yum groupinstall gnome desktop but it wouldn't even install gnome-shell (I did install gnome-shell manually but I only get the shell, absolutely nothing else, not even the calculator)). So, my question is: Shouldn't in _theory_ `yum (re)install @kde-desktop' install everything required for a full KDE install? Thanks in Advance, -- Pedro

2 2

Very rough storage validation matrix draft
by Adam Williamson 02 Apr '14

02 Apr '14

Hi, folks. So, our current set of storage validation tests is just a grab-bag of stuff we've held over from oldui, added and patched piecemeal; it's not very coherent or consistent and it doesn't come close to exercising all of the storage stuff in the installer. We wind up sort of inventing test plans particularly for custom partitioning as we go along, with the consequence that we're not sure what we're going to test, what's really important to test when, etc etc. I've made a few abortive tries at re-doing the storage tests and basically given up because it's just a hideous thing to try and cover, but I thought while I'm still on a momentum roll from F20 and remember some of the issues that came up during F20 validation, I'd take another cut at it. Here's what I came up with: https://fedoraproject.org/wiki/User:Adamwill/Draft_storage_matrix The proposal is to separate out storage testing from the 'installation testing' matrix as its own matrix, because I think we can get further with flexible columns, and it's such a big area the installation matrix gets pretty unwieldy with all the storage tests stuffed into it. remember this is *extremely* rough. It may be that we don't think my organizational approach here is right at all and we should tear it up and start over. But I thought I'd throw it out there for comments. Most of the tests, obviously, don't exist yet; they'd be fairly trivial to write, I think the hard part of the problem here is deciding what we want to test, and how to organize it. It's an extremely difficult area; there are so many different variables to storage configuration that it's utterly impractical to try and cover every possible permutation even assuming the user uses the interface perfectly. What I've tried to do is come up with something which would exercise most of the areas we really seem to want to care about, without being utterly unwieldy. It is still very large, that's probably the first thing you'd notice about it. I doubt we could run this on every build. What I think would be a nice complement is a somewhat improved version of testcase_stats - http://testdays.qa.fedoraproject.org/testcase_stats/ - which could track both dimensions of each matrix, so we could try to strategically ensure every spot on the table is covered at least once per milestone or once per release, say. Here's a quick key to the test names for tests I've made up which may not be self-explanatory, yell if you need explanations of any of the others: ----- guided_multi_empty - the 'multi' means multiple disks, this is checking we correctly autopart to multiple disks. in the custom tests, 'auto' means 'using the autopart mechanism inside custom partitioning', the blue text that lets you automatically create a set of volumes. existing_retain_home - this is the classic 'install over an existing Fedora install, retain the /home partition' trick. existing_precreated - this would be a test for running the installer with a set of empty volumes that you just wanted to assign mount points to. add_to_container - add a new volume to free space within an existing container. assign_* tests - these are for specifying that a given partition or container must be on a particular disk. help_text - just checks the 'help' screen works. small_disks - this would be a test where you check anaconda correctly refuses to install to a disk that's too small. cancel_encryption - this would be to check what happens if you cancel out of the 'enter a passphrase' dialog. shrink_maximum - try to shrink a partition to the largest possible size (right-hand end of the slider) shrink_minimum - shrink a partition as small as possible (left-hand end of the slider) shrink_no_size_change - set action for a partition to 'shrink' but don't actually change its size shrink_unusual_sizes - this would be for the bug we discovered in f20, test the shrinker handles partitions with 'weird' sizes shrink_change_action - this is just for changing the 'action' in shrink a bunch of times and making sure it doesn't explode multiple_trips - run through Installation Destination more than once custom_resize_no_size - just clear the 'desired size' field for a partition and hit 'update settings' custom_resize_invalid_unit - try entering something like '30 ZX' in the desired size field custom_resize_return - change the desired size and then change it back to the original value custom_invalid_mount_point - try entering a mount point name that is not allowed (invalid characters, spaces or something) custom_invalid_filesystem - try putting a system partition on vfat or bios boot or swap or something ---- Please, absolutely all comments, suggestions, alternative proposals, flames etc etc welcome. I'm sure we could improve this proposal or do better, but I think we have to try and do _something_ better than our current tests. And I think drawing up a table like this, if nothing else, illustrates what a hard task this is... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

5 26

any advice to fix firefox being excruciatingly slooooooooow?
by Robert P. J. Day 02 Apr '14

02 Apr '14

since upgrading to rawhide, numerous operations in firefox are just glacially slow -- playing videos results in jerky motion, scrolling has a significant time lag, even typing in a search term in youtube might take several *seconds* before the first letters i typed even display. i've gone into "about:config" and turned off several features but that hasn't helped noticeably. anyone else running across this? any simple advice? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================

10 22

Introduction
by Fidel Leon 31 Mar '14

31 Mar '14

Hi people, I've been using Fedora for a couple of months after an hiatus in the "dark $ide"... I've been using many Linux flavors before, but always feel like "returning home" when using Fedora. So, let me introduce myself. My name is Fidel, I'm 45 and live near Barcelona. I was a SCO (ugs!) Xenix/Unix specialist back in the day (that means early 90s), when I remember I was acquainted of some Slackware 0.99 (and 40+ 3.5" floppy disks). I've been using many hats (administration, development) although my programming experience is mainly in... VB6... Hey, that's what paid my bills! Anyway, I'm learning Python and know C/C++ basics. And have configured everything from netbooks to Linux+Windows AD relationships, and had a short stint as a sysadmin for a humble ISP. That's why I believe I can give something back to Fedora and help testing. I speak Spanish (es_ES), Catalan (ca_CA) and English, and can read French (fr_FR). I have elemental knowledge of Slovenian (sl_SL) and Serbian (sr_SR). So, I can help with i18n and l10n too. Regards, -- Fidel Leon fidelleon(a)mykolab.com AA34 074D 4763 2203 C1B1 7DD7 2107 DB9A AD74 FB97

2 1

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