From Fedora Project Wiki
(Default key-values for basic test classes) |
No edit summary |
||
| Line 1: | Line 1: | ||
== Result == | == Result == | ||
=== Database schema === | |||
[[Image:Autoqa_resultdb_dbschema_4.png]] | [[Image:Autoqa_resultdb_dbschema_4.png]] | ||
[[File:Autoqa_resultsdb_database.sql]] | |||
Testrun is the representation of the whole test result. The test this testrun represents may implement more phases (one testrun may contain 0..* phases) - All we worry about in test phase is it's name and result). | Testrun is the representation of the whole test result. The test this testrun represents may implement more phases (one testrun may contain 0..* phases) - All we worry about in test phase is it's name and result). | ||
| Line 8: | Line 11: | ||
Each test may return additional data (in key-value format) which it needs to store (e.g. compose date, envra,...) - TestrunData is the place to store these. | Each test may return additional data (in key-value format) which it needs to store (e.g. compose date, envra,...) - TestrunData is the place to store these. | ||
=== Default key-values for basic test classes === | === Default key-values for basic test classes === | ||
Revision as of 12:33, 13 April 2010
Result
Database schema
File:Autoqa resultsdb database.sql
Testrun is the representation of the whole test result. The test this testrun represents may implement more phases (one testrun may contain 0..* phases) - All we worry about in test phase is it's name and result).
If one needs to encapsulate more testruns into one (merely imaginary) unit, it's possible to aggregate those testruns using Job (one job may contain 0..* Testruns).
Each test may return additional data (in key-value format) which it needs to store (e.g. compose date, envra,...) - TestrunData is the place to store these.
Default key-values for basic test classes
Installation tests
- release_name
- compose_date
- arch
Repository tests
- repo_name
- compose_date
- arch
Package tests
- name
- envr
- arch
Recommended:
- koji_tag
Specific keyval examples - tests using Bodhi hook:
- bodhi_tag/request -- to mark in which state in Bodhi the package was
Specific keyval examples - comparative tests:
- counterpart_name
- counterpart_envr
- counterpart_koji_tag
- counterpart_bodhi_tag/request, ...
Idea 1
Idea 2 (UML)
Idea 3 (UML)
