#138: ResultsDB: media wiki as a storage for metadata about tests ----------------------------+----------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: major | Milestone: Resultdb Component: infrastructure | Version: 1.0 Keywords: | ----------------------------+----------------------------------------------- Once #135 #136 and #137 are finished, we should create a provider/middle man (probably a library) which will allow us to get information about the respective test and use it for test execution/storing results/displaying results via frontends...
#138: ResultsDB: media wiki as a storage for metadata about tests -----------------------------+---------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: new Priority: major | Milestone: Resultdb Component: infrastructure | Version: 1.0 Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by wwoods):
the master branch of autoqa now has wiki.py, which contains some code for fetching data from the wiki. See http://fedoraproject.org/wiki/QA:Test_Plan_Metadata_Test_Page for an example of properly-encoded wiki/json data.
For this ticket to be finished we need to define/document some required/recommended/optional keys that we expect to be present (that's ticket #137).
This ticket concerns putting wiki.py (or something like it) in resultsdb and making sure it has everything it needs to get the data from the wiki.
#138: ResultsDB: media wiki as a storage for metadata about tests ----------------------------+----------------------------------------------- Reporter: jskladan | Owner: Type: task | Status: closed Priority: major | Milestone: Resultdb Component: infrastructure | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by jskladan):
* status: new => closed * resolution: => fixed
autoqa-devel@lists.fedorahosted.org
-
fedora-badges