From Fedora Project Wiki

No edit summary
(phabricator is discontinued)
 
(30 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= What is ResultsDB =
== What is ResultsDB ==


ResultsDB is a database, in which we'll store results of tests executed by the AutoQA framework.
ResultsDB is a system for storage of test results. It was originally intended to hold the results of tests executed by the [[Taskotron]] framework, but has been intentionally designed to allow storage of results from many different test systems and types of test.


== Motivation behind ResultsDB ==
ResultsDB is only a system for storing test results, different 'frontend' apps can be created using ResultsDB as a data source. These frontends could be anything from a simple tool aggregating recent results for builds, or anything more complicated like a tool for gathering test-related metrics (historical fail/pass ratio of a specific test in a Fedora release, failure rate of critpath packages etc.).


At the moment, all the results are stored on the autoqa-results mailing list [1]. Although this is not really a bad system for storing the results, searching for some particular result (even as simple query as "All results for foobar-1.3-fc15") is not really comfortable. ResultsDB's main purpose is not really to store the data, but to provide easy access to the results via some simple querying API.
== Current state ==


This means, that using the ResultsDB as dabase backend, many 'frontends' can be created. Be it simple tools which will just aggregate most recent results for specified package (maybe a table inside koji/bodhi info pages), some statistical tool for gathering fail/pass ratio of *insert test name of your choice* for given Fedora release, etc.
ResultsDB is currently in its second major version. [https://taskotron.fedoraproject.org/resultsdb/results Fedora's ResultsDB deployment] is used to store results from [[Taskotron]], [https://openqa.fedoraproject.org openQA], and [https://apps.fedoraproject.org/autocloud/ Autocloud].


= Current state =
== Current development version ==


From development point of view, there is quite well-defined database schema [2], 'input' API [3], and proof-of-concept TurboGears2 application [4], implementing these two.
The project is split into these parts:
* [https://pagure.io/taskotron/resultsdb ResultsDB core], which is the implementation of the datastore, and the API provider.
* [https://pagure.io/taskotron/resultsdb_api ResultsDB Client Library] providing the easy-to-use python implementation of the ResultsDB API, with [http://docs.resultsdb20.apiary.io/ documentation]
* [https://pagure.io/taskotron/resultsdb_frontend ResultsDB Frontend] - a simple frontend intended for browsing the results via web interface.


I have also started to work on a proof-of-concept frontend [5], which will allow us to create test plans (like Package Update Acceptance Testplan [6]), using mediawiki pages to define the testplan's requirements [7], [8] (this will be covered in more detail further in the text).
== Discussion ==


Development of ResultDB is discussed on the {{fplist|qa-devel}} mailing list. There is also a {{fplist|resultsdb-users}} list for discussing issues related to 'using' ResultsDB - in the sense of submitting results to or consuming results from a ResultsDB instance.


= Links =
== Contributing ==


* [1] https://fedorahosted.org/pipermail/autoqa-results/
Issues and code changes for ResultsDB are tracked in the Pagure repositories linked above. The individual projects have README files with detailed instructions on setting up development environments in order to be able to run tests and so on.
* [2] https://fedoraproject.org/wiki/AutoQA_resultsdb_schema
 
* [3] https://fedoraproject.org/wiki/AutoQA_resultsdb_API
[[Category:ResultsDB]]
* [4] https://www.assembla.com/code/resultsdb/git/nodes?rev=devel
[[Category:Taskotron]]
* [5] https://www.assembla.com/code/resultsdb_puatp/git/nodes?rev=master
* [6] https://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan
* [7] http://fedoraproject.org/wiki/QA:Test_Plan_Metadata_Test_Page
* [8] https://fedoraproject.org/wiki/User:Jskladan/Sandbox:Package_Update_Acceptance_Test_Plan_Metadata

Latest revision as of 12:51, 7 August 2017

What is ResultsDB

ResultsDB is a system for storage of test results. It was originally intended to hold the results of tests executed by the Taskotron framework, but has been intentionally designed to allow storage of results from many different test systems and types of test.

ResultsDB is only a system for storing test results, different 'frontend' apps can be created using ResultsDB as a data source. These frontends could be anything from a simple tool aggregating recent results for builds, or anything more complicated like a tool for gathering test-related metrics (historical fail/pass ratio of a specific test in a Fedora release, failure rate of critpath packages etc.).

Current state

ResultsDB is currently in its second major version. Fedora's ResultsDB deployment is used to store results from Taskotron, openQA, and Autocloud.

Current development version

The project is split into these parts:

Discussion

Development of ResultDB is discussed on the qa-devel mailing list. There is also a resultsdb-users list for discussing issues related to 'using' ResultsDB - in the sense of submitting results to or consuming results from a ResultsDB instance.

Contributing

Issues and code changes for ResultsDB are tracked in the Pagure repositories linked above. The individual projects have README files with detailed instructions on setting up development environments in order to be able to run tests and so on.

Retrieved from "https://fedoraproject.org/w/index.php?title=ResultsDB&oldid=499248"