#268: Rename lib/python to lib/autoqa
----------------------+-----------------------------------------------------
Reporter: jskladan | Owner:
Type: task | Status: new
Priority: minor | Milestone: Finger Food
Component: core | Keywords:
----------------------+-----------------------------------------------------
It would make more sense to have it named as 'autoqa' rather than 'python'
- e.g. when we want to import the library from inside the git, etc.
Of course, adequate changes need to be made in Makefile and autoqa.spec
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/268>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#300: Do envra conversions with autoqa.util.envra()
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
In ticket #295 we added a new function autoqa.util.envra() for rpm
namespec string conversion. The task is now to go through our code and
make sure we use this function everywhere instead of manually searching
for and stripping by columns, periods, etc.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/300>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#295: Provide proper functions for ENVRA manipulation
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
Some testcases need to manipulate ENVRA names, like stripping epoch,
stripping architecture, detecting whether build name contains epoch,
parsing out package name, etc. The current implementation (taken from
depcheck) is clearly sub-optimal, because it doesn't reflect the full RPM
naming spec, just the most widespread usage (e.g. can colon be part of
NVR, except for separating epoch?):
{{{
def strip_epoch(rpmstr):
return rpmstr.split(':',1)[-1] # works for E:N-V-R.A or N-V-R.A
def strip_arch(rpmstr):
return rpmstr.rsplit('.',1)[0]
}}}
Let's create one or more methods for these tasks in our library and let's
use rpmUtils module in them. That ensures that the correct algorithms for
detecting epochs, names, releases, etc are used.
Most of the use cases for those methods have been mentioned in the
description, but search through available code whether some more use cases
are needed.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/295>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#272: Tell test which arch it is supposed to test
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
Some tests need to know which architecture to check. But currently we
don't pass that information (in the control file). The test can take a
guess by detecting operating system architecture (not hardware
architecture), but that's an ugly workaround. Pass the architecture info
from autoqa script to the test.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/272>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#299: Allow rpmguard to compare to previous releases
-------------------------+--------------------------------------------------
Reporter: orion | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Future tasks
Component: tests | Keywords:
-------------------------+--------------------------------------------------
I have many packages that I only build once a release. Comparing those
builds to previous releases would still be useful I think.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/299>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project