Tests storing results into the ResultsDB - first spin

[Josef Skladanka]

Hello, gang,

I've created a patch, which allows AutoQA tests to store results in resultsdb.
Because of the quite nice design provided by the AutoQATest base class, it's
only new files, and few changes in the base class (23 lines to be exact) :)

Not that I'd want to push it to master or so - just happy that it's working
and the changes were as simple as i hoped :)

Either have a look at the jskladan branch in git, or at the attached patch.

Joza

[Will Woods]

On Fri, 2010-09-03 at 09:24 -0400, Josef Skladanka wrote:
> Hello, gang,
>
> I've created a patch, which allows AutoQA tests to store results in resultsdb.
> Because of the quite nice design provided by the AutoQATest base class, it's
> only new files, and few changes in the base class (23 lines to be exact) :)
>
> Not that I'd want to push it to master or so - just happy that it's working
> and the changes were as simple as i hoped :)
>
> Either have a look at the jskladan branch in git, or at the attached patch.

Whoa! Exciting stuff! Now, of course, we need to start thinking about
frontends to display the test results...

Anyway - the module name 'logging' is kind of confusing, since it
collides with the python 'logging' module (but does something completely
different!). Maybe it should be 'resultsdb'? That's pretty typical for
the module name for the client of an xmlrpc-style service (See also:
import koji, import bugzilla)..

One longer-term possibility - since we plan to have ResultsDB as a
standard, well-integrated part of the Fedora infrastructure, it might be
a good idea to look at the 'fedora.client' modules (in the
'python-fedora' package) and see if we can put the resultsdb client code
in there. Then we'd be giving the whole project easy access to
read/write resultsdb...

-w

[Josef Skladanka]

Great to hear that you like it! Frontends... Guess I'll need to dig into 
the Turbogears2 once again :)

Changing the name is definitely a good suggestion, i'll go with 
resultsdb as you suggested.

That is an interesting idea, but i'd rather do such a thing once the API 
(and the library itself) is at least a bit stabilized - don't want to 
spam the poor guys with dozens of pathes a week ;-)

Thanks for the comment! Made me really happy

joza

On 09/03/2010 05:40 PM, Will Woods wrote:
> Whoa! Exciting stuff! Now, of course, we need to start thinking about
> frontends to display the test results...
>
> Anyway - the module name 'logging' is kind of confusing, since it
> collides with the python 'logging' module (but does something completely
> different!). Maybe it should be 'resultsdb'? That's pretty typical for
> the module name for the client of an xmlrpc-style service (See also:
> import koji, import bugzilla)..
>
> One longer-term possibility - since we plan to have ResultsDB as a
> standard, well-integrated part of the Fedora infrastructure, it might be
> a good idea to look at the 'fedora.client' modules (in the
> 'python-fedora' package) and see if we can put the resultsdb client code
> in there. Then we'd be giving the whole project easy access to
> read/write resultsdb...
>
> -w
>
> autoqa-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/autoqa-devel