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=f4eddb95763e61398c0cdfd6d5fd35e3a661707a
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?rev=f4eddb95763e61398c0cdfd6d5fd35e3a661707a
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_testcases 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
Heh, sent the email and did not really write all i wanted so:
You can start Jobs from the Testplan view, start Testruns (more fun!) from Testcase view.
You can then list the details on the Jobs/Testruns pages (e.g. http://10.34.31.238/wsgi/resultsdb/frontend/input_fake_data?action=job_detail&id=1 http://10.34.31.238/wsgi/resultsdb/frontend/input_fake_data?action=testrun_detail&id=6)
If you're interested in the code behind the scenes, then sit down, have a cool drink and look at this (don't get scared, it's ugly!) http://www.assembla.com/code/resultdb/git/nodes/wsgi/frontend/input_fake_data.py?rev=f4eddb95763e61398c0cdfd6d5fd35e3a661707a
Joza
On 06/09/2010 06:50 PM, Josef Skladanka wrote:
Hello gang,
I'd like to give you heads up on current ResultsDB state:
- The 'Input' API is working and IMHO OK
These functions are made public via xmlrpc interface http://10.34.31.238/wsgi/resultsdb/xmlrpc.
- 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?rev=f4eddb95763e61398c0cdfd6d5fd35e3a661707a
- 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_testcases 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
autoqa-devel mailing list autoqa-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/autoqa-devel
autoqa-devel@lists.fedorahosted.org