[Fedora QA] #202: Create test case for firstboot (graphic and text)
by fedora-badges
#202: Create test case for firstboot (graphic and text)
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
Per #151, we are missing test cases for firstboot functionality, which is
required by Alpha release criterion "In most cases (see Blocker_Bug_FAQ),
a system installed according to any of the above criteria (or the
appropriate Beta or Final criteria, when applying this criterion to those
releases) must boot to the 'firstboot' utility on the first boot after
installation, without unintended user intervention. This includes
correctly accessing any encrypted partitions when the correct passphrase
is supplied. The firstboot utility must be able to create a working user
account". We should create a test case to verify this requirement and add
it to the matrices. Assigning to myself for now, but anyone else, feel
free to jump in!
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/202>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #219: Create virtualization installation validation test cases
by fedora-badges
#219: Create virtualization installation validation test cases
-----------------------------------------+----------------------------------
Reporter: adamwill | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 16
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
As per the Beta criteria survey in https://fedorahosted.org/fedora-
qa/ticket/151 , there are no test cases to enforce the Beta release
criteria:
"The release must boot successfully as a virtual guest in a situation
where the virtual host is running the same release (using Fedora's current
preferred virtualization technology)"
"The release must boot successfully as a virtual guest in a situation
where the virtual host is running the previous stable Fedora release
(using Fedora's current preferred virtualization technology)"
"The release must boot successfully as a virtual guest in a situation
where the virtual host is running a supported Xen implementation"
We should create test cases to explicitly cover these criteria, especially
the Xen one, which we do not usually test at present (the other two
usually get covered in practice, although we don't have explicit test
cases for them).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/219>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #244: Cloud SIG Test Day
by fedora-badges
#244: Cloud SIG Test Day
----------------------+-----------------------------------------------------
Reporter: rbergero | Owner:
Type: defect | Status: new
Priority: major | Milestone: Fedora 16
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
At bare minimum right now:
* Fedora EC2 images
* OpenStack
We'd like the last slot, on 10/20.
-Robyn
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/244>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #230: QA:Testcase_Anaconda_autopart_(encrypted)_install overlaps with QA:Testcase_base_startup
by fedora-badges
#230: QA:Testcase_Anaconda_autopart_(encrypted)_install overlaps with
QA:Testcase_base_startup
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
See summary. With the new 'base' matrix, I made startup a separate 'base'
test - it's not really part of installer testing. The
QA:Testcase_Anaconda_autopart_(encrypted)_install includes startup
testing. I think it'd be best to shorten that test case, and make a note
in it that testing whether the installed system successfully boots is part
of the base_startup test.
assigning to me, but if anyone else wants to take over, go for it...
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/230>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #220: Review RHBZ #704030 with rel-eng to identify cause and make appropriate SOP changes to ensure issue is not repeated
by fedora-badges
#220: Review RHBZ #704030 with rel-eng to identify cause and make appropriate SOP
changes to ensure issue is not repeated
----------------------+-----------------------------------------------------
Reporter: jdulaney | Owner: jdulaney
Type: defect | Status: new
Priority: major | Milestone: Fedora 16
Component: Trac | Version:
Keywords: |
----------------------+-----------------------------------------------------
During the media creation process, if --excludes is not explicitly in the
repo definition, then packages get pulled in that cause package conflicts.
For example, astronomy-bookmarks-1-7.fc15.noarch xor fedora-
bookmarks-15-0.1.noarch, but not both.
There needs to be a patch for rel-eng to specify that this be done and
checked for every time a release/release candidate is composed.
This is to follow with the Alpha Release Criterion:
"There must be no file conflicts (cases where the files in some packages
conflict but the packages have explicit Conflicts: tags are acceptable) or
unresolved package dependencies during a media-based (CD/DVD) install "
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/220>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #154: Tracker: critical path test case creation
by fedora-badges
#154: Tracker: critical path test case creation
-------------------------+--------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Wiki | Version:
Keywords: |
-------------------------+--------------------------------------------------
= problem =
We need more specific per-package guidance for proven tester testing, to
make sure the testing covers all the relevant critical path functionality
of each package.
= enhancement recommendation =
We can create a group of test cases in the Wiki for each critical path
package. Bodhi could integrate with this system and, in the future non-
numeric karma system, provide checkboxes for each test case for packages
which have test cases available. fedora-easy-karma could provide an
interface to display and check off test cases from the Wiki.
This ticket can serve as a tracker for this process, which will be
ongoing. To start with I will file tickets for each package which has so
far been identified (on test and devel mailing lists) as an obvious
candidate for such test cases, with a note of what should be covered for
each package. Those tickets will block this one.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/154>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months
[Fedora QA] #80: Add dual-boot release criteria
by fedora-badges
#80: Add dual-boot 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=590661
RHBZ#590661 - GRUB bootloader should have a few seconds delay on a multi-
boot setup]
= analysis =
Due to RHBZ #590661, the dual-boot experience was not well understood and
tested for the final release. It was discovered late and unclear whether
this behavior was critical to Fedora success.
= enhancement recommendation =
The user experience of dual-boot scenarios was not well understood, as a
result RHBZ #590661 did not clearly impact the release criteria.
Recommend reviewing and making adjustments to the release criteria for
dual-boot expectations.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/80>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 3 months