#170: Request for F15 Power Management test day
-----------------------------------------+----------------------------------
Reporter: jskarvad | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
We would like to have the Power Management test day on 2011-03-24 (or
maybe later). Such event would help us to test the PM functionality
(especially suspend / hibernate and tuned profiles) across wide HW
configurations. We are able to prepare detailed test instructions and
scripts for test semi-automation. Feature page:
https://fedoraproject.org/wiki/Features/PowerManagementF15
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/170>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#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
#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
Greetings folks,
Just wanted to summarize how testing held up for the pre-beta acceptance test run of Fedora 15. Thanks for your attention. It is a good news that the pre-RC installation version has passed the major test, which is used to identify any major test blockers prior to the Test Compose (TC).Let's expect the exciting coming out of F15-TC1 next week!
If you have spare time and want to contribute by verify this version, the test cases and results can be found on the following URL:
https://fedoraproject.org/wiki/Test_Results:Fedora_15_Pre-RC_Acceptance_Tes…
Thanks a lot!
Good Luck,
Tao Wu
This is kind of half a memo-to-self, but of course, the more people who
help out, the merrier :)
So we have various housekeeping tasks that come under the Bugzappers
umbrella, and may have been neglected lately:
https://fedoraproject.org/wiki/BugZappers/HouseKeepinghttps://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora15
since we haven't run a Bugzappers meeting for a while we should check up
on these and make sure they're happening; it may make sense to pull them
into the QA process instead of Bugzappers, or just run a BZ meeting to
look after them.
If anyone is already working on this, or has a good plan, do speak up!
Otherwise I'll look at doing something about it.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
#116: Clarify https://fedoraproject.org/wiki/QA:Testcase_Mediakit_FileConflicts
to say that explicit Conflicts: are acceptable
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: rhe
Type: defect | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
= bug description =
Please update the
https://fedoraproject.org/wiki/QA:Testcase_Mediakit_FileConflicts test
case to clarify that explicit Conflicts: tags are okay.
= bug analysis =
The relevant release criterion is "No file conflicts or unresolved package
dependencies during a media-based (CD/DVD) install". The term "file
conflicts" here is important. I believe it's intended to mean that only
cases where the files in two packages conflict, but there is no explicit
Conflicts: tag in the packages. Where the conflict is properly marked in
the packages with Conflicts: tags, this should not be considered an
infringement of the criterion.
= fix recommendation =
Change expected results:
2. No file conflicts were detected for packages included in the media kit,
unless the conflicting packages also have explicit Conflicts: tags
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/116>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#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
#194: proven tester request
-----------------------------------------+----------------------------------
Reporter: sanchez | Owner:
Type: proventester request | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Hi all,
I would like to join the Fedora project actively, and I believe testing
packages could be my first step on the project. I do have experience with
Linux for many years now, as a professional as well as a hobbyist. I can
also do some scripting with python and bash and always had interest in
opensource, testing, GPL , HA clustering etc.
Salud!,
Raúl,
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/194>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
#86: Add test coverage for text-mode upgrade
---------------------------+------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
See [http://bugzilla.redhat.com/590823 RHBZ#590823 - Text-mode upgrade
fails when installing new bootloader -- KeyError: 'bootloader']
= analysis =
Some tests in the
[https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
install test matrix] involve user interface components in both text-mode
and graphical-mode (native or VNC). One such bug (RHBZ #590823) involved a
problem found only during text-mode upgrades to Fedora 13. The text-mode
upgrade screen shows different options thanenhancement recommendation =
= enhancement recommendation =
I'm hesitant to recommend specific text-mode tests for each user interface
element that differs in text-mode and graphical-mode (it would be
exhaustive but unachievable). As a catch-all, testing a text-mode install
is included in the current matrix. Is there something small that can be
done to cover the gap?
1. Perhaps adding a text-mode upgrade test case to the install matrix, or
...
2. Adding variations to the existing upgrade tests
[https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Update_Bootload…
QA:Testcase_Anaconda_Upgrade_Update_Bootloader] and
[https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Skip_Bootloader
QA:Testcase_Anaconda_Upgrade_Skip_Bootloader] to also test text-mode, or
...
3. <insert better idea here>
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/86>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance