[Fedora QA] #98: Request for a Mentor
by fedora-badges
#98: Request for a Mentor
-----------------------------------------+----------------------------------
Reporter: jdulaney | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
I would like to now formally request a Proven Tester Mentor. I have been
running Fedora since FC1, generally updating every other release (I
skipped 9 and went straight to 10). I have several boxes so as to get
different hardware involved.
Thanks,
John H. Dulaney
https://fedoraproject.org/wiki/User:Jdulaney
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/98>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #60: Devise a better location for critpath.txt
by fedora-badges
#60: Devise a better location for critpath.txt
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
-------------------------+--------------------------------------------------
critpath.txt lists critical path packages [1]. Currently it is referenced
as
{{{
http://kojipkgs.fedoraproject.org/mash/rawhide-<<CURRENT
DATE>>/logs/critpath.txt
}}}
or
{{{
http://kojipkgs.fedoraproject.org/mash/rawhide-<<YESTERDAY
DATE>>/logs/critpath.txt
}}}
depending on which page. Similarly for branched releases.
This is not optimal. Very often the url just doesn't work. For example at
the time of writing critpath.txt on F13 Alpha Release Criteria page [2]
references rawhide-20100407/ directory, where critpath.txt is not
available. Nor it is available in rawhide-20100406/ directory. Only in
rawhide-20100405/ it is finally available.
The very page Critical Path Packages [1] references critpath.txt for
Branched release, which is available ATM, but also references critpath.txt
for Rawhide, which is again not available.
Let's imagine other use case - some automated tool must decide whether
package in the critical path. It can't rely on path which are constantly
changing and sometimes are not available.
critpath.txt is created dynamically, so we probably must have the contents
created every day or so. But we should devise such mechanism that the
location is stable and the file is always available (if new contents fails
to create, the old contents is still available). That will also allow
third-party tools to rely on it.
[1] https://fedoraproject.org/wiki/Critical_Path_Packages [[BR]]
[2] https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/60>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #134: Clarify the ISO to USB tests
by fedora-badges
#134: Clarify the ISO to USB tests
-------------------------+--------------------------------------------------
Reporter: rhe | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Test Review | Version:
Keywords: |
-------------------------+--------------------------------------------------
We've heard many users installing by writing ISO to USB drive and having
problems about it. So it's better to have a clear story from anaconda or
whoever on what exactly is supported in terms of writing the DVD image to
USB, and what isn't. It would be good to clear it up and add some specific
install validation tests for it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/134>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 8 months
[Fedora QA] #79: Add firstboot release criteria
by fedora-badges
#79: Add firstboot 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=574596
RHBZ#574596 - Smolt does not run at firstboot]
= analysis =
We don't have a way to know what firstboot modules are expected, we need
to document this as release criteria, or write a test to report the issue
(for details, see RHBZ #574596).
= enhancement recommendation =
The release criteria do not include what
image:Package-x-generic-16.pngfirstboot modules are intended for Fedora.
Often, firstboot some modules are missing or disabled, and we don't notice
or know whether this is a blocker. Recommend clarifying the use cases of
firstboot in the release criteria.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/79>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 8 months
[Fedora QA] #84: Define install matrix baseline
by fedora-badges
#84: Define install matrix baseline
---------------------------+------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
* We almost didn't find [http://bugzilla.redhat.com/578633 RHBZ#578633 -
Unable to enter passphrase to unlock encrypted disk partitions]
* When re-using test results from a previous test run, it's possible to
include results for tests that should be re-tested. This would be bad.
= analysis =
* F-13 Beta candidate#3 didn't include the correct version of
''plymouth'' (see RHBZ #578633).
* Since it was Beta#3 and not much was supposed to change from Beta#2,
some test results from the previous Beta#2 candidate were carried forward.
* Thankfully, QA found the problem before release while running the
QA:Testcase_Anaconda_autopart_(encrypted)_install test.
= enhancement recommendation =
* Establish better guidelines about which test results can be carried
forward from one candidate to the next (this isn't easy). Or perhaps,
establish a subset of tests that all respins must undergo.
* Perhaps link to, or document at
http://fedoraproject.org/wiki/QA:Installation_validation_testing
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/84>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 10 months
[Fedora QA] #158: Proposed Test Day - l10n/i18n test day
by fedora-badges
#158: Proposed Test Day - l10n/i18n test day
----------------------+-----------------------------------------------------
Reporter: rhe | Owner: rhe
Type: task | Status: new
Priority: major | Milestone: Fedora 15
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
As discussed with Igor, this test day will be hosted on 2011-03-03. [[BR]]
Igor, have you figured out which features/areas you want to target on? Do
you plan to use the l10n template and specific test results page for it or
the formatted wiki test day result page as before? [[BR]]
Thanks.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/158>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 1 month