RE: Very Rough Code for Mock Fedora Infrastructure
----------------------------------------
Date: Thu, 28 Jul 2011 11:49:53 -0600
From: tflink(a)redhat.com
To: autoqa-devel(a)lists.fedorahosted.org
Subject: Re: Very Rough Code for Mock Fedora Infrastructure
On Thu, 28 Jul 2011 11:45:36 -0600
Tim Flink <tflink(a)redhat.com> wrote:
> This kept falling off my TODO list, but I finally got what I have for
> initial mock Fedora infrastructure code up on github:
Yay for sending emails by accident after typing the first sentence!
Anyways, the code is up on github:
- https://github.com/tflink/mock_fedorainfra
As a warning, the code is _VERY_ rough right now - barely enough to be
called a proof of concept. Not much in the way of documentation and
everything is static right now - queries on any package will always
return the same information.
I know that John was interested in working on this and I don't know if
he had started or not but figured that this code might be useful. I can
add documentation, clean the stuff and give explanations if desired.
Tim
Hey, Tim
Thanks much for this. I had indeed done some work on the actual
mockups, but so far most of my work so far has been in setting up
the actual tests; it looks like that code could be easily integrated with
what you've got to create a final project. I'll go through it today and
get it presentable and try to get it on Review Board by early this
evening. It looks like my code would replace your pytests.sh script.
In a nutshell, it creates the virtual environment, loads up mock Koji
and mock Bodhi (I hadn't finished with these, I'll change the code to
point to your work) and populates mock Koji and Bodhi with sets of
test packages chosen to give specific results from AutoQA depending
on the actual test cases. It then compares that output from AutoQA
to what is expected and reports on inconsistencies. No report means
everything is hunky dory. It then proceeds to the next test listed in
the file. When it's all done, it spits out a log of passed and failed tests.
I chose to go with a batch style setup because I figured that this would
be a good start it and ignore it until its done situation.
Like I said, I'll try my best to get things ready by this evening; Monday
at the latest.
John.