#443: Better format for test compose (TC) and release candidate (RC) requests
----------------------------------------+------------------------
Reporter: jreznik | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 21
Component: Blocker/NTH review process | Version:
Keywords: | Blocked By:
Blocking: |
----------------------------------------+------------------------
= problem =
With Dennis (in CC), we discussed how to make release process, with
Fedora.next in mind, more transparent and bullet proof. One issue is that
releng request can become pretty messy, with full text included and
sometimes it leads to errors (omission of packages in compose etc).
= enhancement recommendation =
One possibility is to visibly separate full text description (with bug
numbers, reasons - it's good to have history) and the list of exact nvrs
(maybe in code block?), try to avoid "qt bundle" etc. so it's easier to
pick up the right list (for blockers, FEs + exceptional tools requests).
Another thing is better coordination between requester/releng - to mark
when/which list was picked up etc, in similar way how Go/No-Go decision is
stated in the ticket.
Now I'll let more space to Dennis, maybe example of how the request should
look like to make it easy to parse would help.
Long term (and preferred) solution would be to have automation in place,
Blocker app talking to releng interface, compose database, web dashboard
etc...
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/443>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#398: Add Secure Boot test case
----------------------+------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 20
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
We don't have an explicit test for doing a Secure Boot install. We should
have one, for the most basic case (install to a system with a typical OEM
SB configuration).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/398>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#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
#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
#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
#454: Proposed Test Day - Server
----------------------+------------------------
Reporter: junland | Owner: junland
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version: 2.0
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
Hello, I would like to proposal a Test Day for F21 Server Beta.
Date: November, 7th 2014 (All-Day)
Testing criteria would be over special features (openLMI, Cockpit, rolekit
etc.) and then a open-test for anyone who want to explore / file bugs
using the server.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/454>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#452: Proposed Test Day - Jenkins
----------------------+------------------
Reporter: msrb | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------
Hi,
I would like to schedule a test day for Jenkins [1].
Proposed test date: 30th September
Thanks
[1]: http://fedoraproject.org/wiki/Changes/Jenkins
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/452>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#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
#449: Proposed Test Day - Cockpit
----------------------+------------------------
Reporter: stefw | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
Ownership: Stef Walter <stefw(a)redhat.com>, Marius Vollmer
<mvollmer(a)redhat.com>
Time frame: Would like a test day allocated late in the test cycle.
Features: https://fedoraproject.org/wiki/Changes/CockpitManagementConsole
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/449>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance