[Fedora QA] #223: F16 Graphics Test Week
by fedora-badges
#223: F16 Graphics Test Week
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 16
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
It's Graphics Test Week time again...
pencilling in for August 30th, 31st and September 1st. I will organize and
put up wiki pages shortly.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/223>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #222: L10N Test Day
by fedora-badges
#222: L10N Test Day
-----------------------------------------+----------------------------------
Reporter: noriko | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
For better translation quality, L10N test day is proposed which will be
same one done in F15.
The proposed date: 2011-08-22
It is ideal to have a test day on 2011-08-22 to leave max amount of time
for translators by the deadline.
2011-08-19 Live image for translation review UI to be composed
2011-08-30 Software Deadline
http://rbergero.fedorapeople.org/schedules/f-16/f-16-trans-tasks.html
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/222>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #205: Create test case for system logging
by fedora-badges
#205: Create test case for system logging
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
Per #151, we are missing a test case for the Alpha release criterion "A
system logging infrastructure must be available and enabled by default. It
must provide at least basic local file-based logging of kernel messages,
and allow other components to write log messages. This must be done in
accordance with relevant standards accepted by the Project". We should
create a test case to validate this criterion, and add it to the matrices.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/205>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #204: Create test case for artwork
by fedora-badges
#204: Create test case for artwork
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
As per #151, we are missing a test case for the Alpha release criterion
"The default Fedora artwork must either refer to the current Fedora
release under development (Fedora 16), or reference an interim release
milestone (e.g. Alpha or Beta). If a release version number is used, it
must match the current Fedora release under development. This includes
artwork used in the installer, firstboot, graphical boot, graphical login
and desktop background." (and also for the Final criterion "The proposed
final Fedora artwork must be included and enabled by default for the
installer, graphical boot, firstboot, graphical login and desktop
background. All Fedora artwork must be consistent with the proposed final
theme, and if any artwork contains a graphical version number, the version
number used must match the Fedora release number. Generic release artwork
(e.g. Alpha, Beta, Development) must not be used for the final release").
We should create one or two test cases to cover these criteria and add
them to the desktop matrix.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/204>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[Fedora QA] #203: Create test case for boot-to-graphical-environment
by fedora-badges
#203: Create test case for boot-to-graphical-environment
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 16
Component: Wiki | Version:
Keywords: |
----------------------+-----------------------------------------------------
Per #151, we are missing an explict test case for the Alpha criterion
"Following on from the previous criterion, after firstboot is completed
and on subsequent boots, 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 a working graphical environment
without unintended user intervention. This includes correctly accessing
any encrypted partitions when the correct passphrase is supplied", though
it is somewhat implied by the more complex desktop test cases. It would be
more correct to have a specific test case for this, however. We should
create one, and add it to the desktop matrix. Assigning to myself for now,
but if anyone else wants to take this, please do!
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/203>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
12 years, 4 months
[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
12 years, 4 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
12 years, 4 months