[Fedora QA] #228: SOPs for Everything
by fedora-badges
#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
9 years, 2 months
[Fedora QA] #429: temporary membership in sysadmin-qa for atodorov so that beaker trial can continue
by fedora-badges
#429: temporary membership in sysadmin-qa for atodorov so that beaker trial can
continue
-------------------------+------------------
Reporter: tflink | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: permissions | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------
= phenomenon =
Long story short, atodorov is helping with the beaker trial we're doing
and he needs shell access to the machine in order to complete his work.
Assuming that this trial is successful, access to the beaker system(s)
will be controlled with a separate FAS group but until that is set up,
sysadmin-qa membership is the only way to get the required access.
I don't expect the need for membership to last any more than a couple of
weeks.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/429>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #403: Modify initial-setup test case or create new one for ARM (vendor mode)
by fedora-badges
#403: Modify initial-setup test case or create new one for ARM (vendor mode)
------------------------+------------------------
Reporter: adamwill | Owner: pwhalen
Type: task | Status: new
Priority: blocker | Milestone: Fedora 20
Component: Test cases | Version:
Keywords: arm | Blocked By:
Blocking: |
------------------------+------------------------
The initial-setup test case -
https://fedoraproject.org/wiki/QA:Testcase_base_initial_setup - doesn't
really cover the case where initial-setup runs in 'vendor mode'. This mode
is currently used only for ARM pre-built images, but since ARM is now
primary arch, we need a test case for it. It should be basically a more
extensive version of the test case that covers all the bits that would be
release blocking for ARM (which I think is language, root password, user
password, date/time - really all of it).
If the existing test case can be 'conditionalized' elegantly enough,
that'd be okay, otherwise just create a variant of it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/403>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #394: Revise validation process / templates for ARM as primary arch
by fedora-badges
#394: Revise validation process / templates for ARM as primary arch
----------------------+------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 20
Component: Wiki | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
ARM has been accepted as a primary arch at least for buildsystem purposes.
The plan is to have 'primary' ARM deliverables as well if possible. This
may require us to revise the validation process / template pages to
incorporate ARM testing. It may be as 'simple' as throwing a couple of
extra columns (for the two ARM variants) alongside x86_64, i686 and EFI in
the templates, but we will have to take a look.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/394>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months
[Fedora QA] #363: Require spins to go through smoke testing before being published
by fedora-badges
#363: Require spins to go through smoke testing before being published
-------------------------+----------------------------------
Reporter: adamwill | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Undetermined Future
Component: Test cases | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+----------------------------------
= problem =
Sometimes, we publish spins that are completely DOA.
= analysis =
There is no mandatory testing of any Fedora images beyond netinst, DVD and
the two release blocking desktop live spins, as things stand, but we
publish rather more spins than that. In practice we test Xfce, LXDE, SoaS
and AMI images to some extent, but others are rarely touched.
= enhancement recommendation =
viking-ice has suggested that we should produce some kind of validation
matrix which has very basic, generic smoke tests: basically, does the
image at least boot up sanely? We would require there to be a PASS for
these mandatory smoke tests present in that matrix for a spin image to be
published on the spins page. QA does not commit to doing the actual
testing; we may do so if we have time, but ultimately, if a spin owner
wants to have their spin published, it's their responsibility to get the
testing done, either by poking QA, doing it themselves, or getting someone
else to do it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/363>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
9 years, 2 months