#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
#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
#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
#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
#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
#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
#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
#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
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/
Proposing a new draft release validation test case:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_Testcase_desktop_term…
this is a fairly simple test case that just checks that a terminal
application works in a desktop environment. It would be added to the
desktop matrix along with the browser test case, to cover the lack of a
test case to enforce the terminal part of the Alpha criterion "It must
be possible to run the default web browser and a terminal application
from all release-blocking desktop environments."
Comments, improvements, suggestions etc welcome as always! As this is
pretty straightforward I'm planning to put it into production pretty
soon if there's no negative feedback.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net