[Fedora QA] #395: Consider how to improve testing of different installer interfaces
by fedora-badges
#395: Consider how to improve testing of different installer interfaces
----------------------+------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 20
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
During the F19 cycle, the anaconda text installer interface became a lot
more capable; it now replicates almost all the functionality of the
graphical UI, only really missing custom partitioning.
However, we still only have a single test case for it -
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Text -
which simply says 'run any old text install you like'. That's a bit weak.
We may want to re-evaluate the most sensible way to test the different
installer interfaces; just having a single test case for each interface
seems a bit of an odd approach. It seems more reasonable to run the
functional test cases against multiple interfaces, though it may be
unrealistic to try and run every test case against every possible
arch/interface combination.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/395>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #273: Improve browseability of validation matrix pages
by fedora-badges
#273: Improve browseability of validation matrix pages
-----------------------------------------+------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 17
Component: Proventester Mentor Request | Version:
Keywords: | Blocked By:
Blocking: |
-----------------------------------------+------------------------
= problem =
cwickert and sandro have told us they have trouble finding the validation
matrix pages when they need them.
= analysis =
we do have the pages logically named and categorized, but it's still not
that easy to, for e.g., see all the desktop result pages for a given
release at a glance.
= enhancement recommendation =
We could add more categories, for example "Fedora XX
{{desktop,base,install}} validation results" categories, and any others
that come to mind (suggestions please!) It would be nice to have 'next /
previous' links that would let you browse from Final RC4 back to Final RC3
back to Final RC2 back to Final RC1 back to Final TC2 back to Final TC1
back to Beta RC4 and so on, but I'm not sure if that's plausible to
implement automatically (it would be relatively easy to do manually when
creating the pages, though).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/273>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #228: SOPs for Everything
by fedora-badges
#228: SOPs for Everything
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 17
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
We should have...SOPs for Everything!
This is a meta-ticket with the aim of identifying, well, everything QA
does, and making sure they all have SOPs. For a start, I'm going to do a
survey of the QA calendar for a release, and check whether we have an SOP
for each task.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/228>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #450: Fedora 21 Translation (L10n) Test Day
by fedora-badges
#450: Fedora 21 Translation (L10n) Test Day
----------------------+------------------------
Reporter: anipeter | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
Translation (L10n) Test Day for Fedora 21 needs to be decided.
Software Translation Deadline : 26th August. ie, we can have the test date
one week before this date for translators to review and fix their
translations and hence propose L10n test date as 19th Aug (Tuesday).
FLTG team will be working towards coordinating and arranging the test day
including creating new test cases, reviewing old test cases, redesign test
page, provide required assistance to get the image for testing, help
testers on test day etc.
Thanks
Ani Peter (ani)
FLTG
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/450>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #447: Proposed Test Day - ARM
by fedora-badges
#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
9 years, 3 months