#448: Proposed Test Day - Virtualization
----------------------+------------------------
Reporter: crobinso | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
I'd like to propose a test day for Virtualization.
Preferred date would be mid to late August.
We will be doing general virt testing, like the standard test cases we
carry over for each test day:
http://fedoraproject.org/wiki/Test_Day:2013-10-08_Virtualization
And likely some specific test cases for our f21 feature:
https://fedoraproject.org/wiki/Changes/Virt_64bit_ARM_on_x86
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/448>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#447: Proposed Test Day - ARM
----------------------+--------------------------
Reporter: pwhalen | Owner: Paul Whalen
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+--------------------------
= phenomenon =
Proposed test day for ARM to occur between Alpha and Beta.
= implementation recommendation =
Testing to include all deliverables and target platforms (including
Allwinner sunxi ARM SoC support).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/447>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#446: Proposed Test Day - NetworkManager
----------------------+------------------------
Reporter: vbenes | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
I would like to schedule a test day for NetworkManager. Anytime between
Alpha and Beta
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/446>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#444: Proposed Test Day - GNOME-3.14
----------------------+------------------------
Reporter: vbenes | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
Hi, would like to schedule a test day for GNOME-3.14.. somewhere between
alpha and beta
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/444>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#441: Sysadmin permission to beaker for desktop qe
-------------------------+------------------
Reporter: vrutkovs | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: permissions | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------
Please add vrutkovs, vhumpa and vbenes to beaker's sysadmin group in order
to work on desktop tests for Fedora. Approved by tflink
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/441>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#429: temporary membership in sysadmin-qa for atodorov so that beaker trial can
continue
-------------------------+------------------
Reporter: tflink | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: permissions | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------
= phenomenon =
Long story short, atodorov is helping with the beaker trial we're doing
and he needs shell access to the machine in order to complete his work.
Assuming that this trial is successful, access to the beaker system(s)
will be controlled with a separate FAS group but until that is set up,
sysadmin-qa membership is the only way to get the required access.
I don't expect the need for membership to last any more than a couple of
weeks.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/429>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#403: Modify initial-setup test case or create new one for ARM (vendor mode)
------------------------+------------------------
Reporter: adamwill | Owner: pwhalen
Type: task | Status: new
Priority: blocker | Milestone: Fedora 20
Component: Test cases | Version:
Keywords: arm | Blocked By:
Blocking: |
------------------------+------------------------
The initial-setup test case -
https://fedoraproject.org/wiki/QA:Testcase_base_initial_setup - doesn't
really cover the case where initial-setup runs in 'vendor mode'. This mode
is currently used only for ARM pre-built images, but since ARM is now
primary arch, we need a test case for it. It should be basically a more
extensive version of the test case that covers all the bits that would be
release blocking for ARM (which I think is language, root password, user
password, date/time - really all of it).
If the existing test case can be 'conditionalized' elegantly enough,
that'd be okay, otherwise just create a variant of it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/403>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#400: Revise 'firstboot' test case
------------------------+------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 20
Component: Test cases | Version:
Keywords: | Blocked By:
Blocking: |
------------------------+------------------------
We've fixed up the release criteria for the F19 changes to replace
firstboot with initial-setup and gnome-initial-setup and allow user
creation in anaconda, but we still have the firstboot test case:
https://fedoraproject.org/wiki/QA:Testcase_base_firstboot
And the startup test case:
https://fedoraproject.org/wiki/QA:Testcase_base_startup
assumes the firstboot path too. We should revise those for the new era and
the new criterion.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/400>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance