Hello gang,
I'd like to give you heads up on current ResultsDB state:
1) The 'Input' API is working and IMHO OK
<
http://www.assembla.com/code/resultdb/git/nodes/resultdb/input_api.py?rev...
These functions are made public via xmlrpc interface
<
http://10.34.31.238/wsgi/resultsdb/xmlrpc>.
2) I'm starting to work on 'Output' API - i.e. functions to dig data
from the database. Since I don't really know what one would like to get
and how to filter the results (server side), it's pretty blunt for now
<
http://www.assembla.com/code/resultdb/git/nodes/resultdb/output_api.py?re...
3) Closely with {2} i started to work on some quick'n'dirty (yeah,
emphasise on the dirty part) project to test resultsdb's functionality
<
http://10.34.31.238/wsgi/resultsdb/frontend/input_fake_data>
First of all, you can view (Testplans, Jobs, Testcases, Testruns) from
the database (if you'd like to add something, use
<
http://10.34.31.238/phpmyadmin/index.php> user = "root", password =
"secret" [without quotes] - please be nice to that machine :-D).
The testplans/testcases in database have it's wiki-page counterparts set
up see either the tool, database or
<
https://fedoraproject.org/wiki/Category:Jskladan_resultsdb_sandbox> for
links.
Why do I say that? Because some of the functionality takes advantage
from the information on the wiki! For example try starting a new testrun
<
http://10.34.31.238/wsgi/resultsdb/frontend/input_fake_data?action=show_t...
the key-value pairs are grabbed from the wiki (hint: try changing the
value of "required_keyval" key on the appropriate wiki page and
refreshing the 'start new testrun' page ;-) - once again, be nice, I
don't really deal with errors, since it's behind the scope of proof of
concept tool)
I'll let the machine (10.34.31.238) running until tomorrow (it's a virt
guest on my notebook), so feel free to play around!
Joza