#125: initscripts: Choosing the right repo for dependencies
-------------------------+--------------------------------------------------
Reporter: kparal | Owner: jskladan
Type: task | Status: new
Priority: major | Milestone:
Component: tests | Version: 1.0
Keywords: initscripts |
-------------------------+--------------------------------------------------
Currently after new Koji build the initscripts test downloads all relevant
binary packages (related to the particular source package) and installs
them. But the RPM dependencies are installed from stable/updates repos,
not from Koji. Also the dependencies parsed out of Makefile are installed
from stable/updates repos.
We have to inquire a little more into this situation. Is it
sufficient/desirable? Or is it desirable to download dependencies from
updates-testing or bleeding edge Koji? May the initscripts test sometimes
fail because of insufficient dependencies are in stable/updates repos?
This also depends on cases when we are going to use initscripts test. If
it will be used with Bodhi hook, it will be probably easier to solve it
than when used with Koji hook.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/125>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#102: post-iso-build hook
----------------------+-----------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: watchers | Version: 1.0
Keywords: |
----------------------+-----------------------------------------------------
We need one (or more) standard locations where new iso images get posted
for testing, and a watcher that can monitor for new iso images and launch
appropriate installation/sanity tests.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/102>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#209: complete auto CD install test driver
-------------------+--------------------------------------------------------
Reporter: liam | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
-------------------+--------------------------------------------------------
complete the cd_install.py as dvd_install.py to support CD install, with
some functions like automatically swap CD when CD1 install was completed.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/209>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#149: rpmlint: Provide whitelisting of messages
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Package update tests
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
We need to provide some whitelisting capability of rpmlint packages, so
the package maintainers can mark some messages as invalid. We will also
probably want to mark some messages as invalid by default for the whole
Fedora project.
As an interesting inspiration, look at lintian project (validation of deb
packages). It provides some "overrides" on a package basis, you just
create a definition file in /etc/lintian/package_name or kind of. I have
the feeling that rpmlint provides something similar, but we need to
discover it more properly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/149>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project