From Fedora Project Wiki
(2 more ideas) |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Result === | |||
[[Image:Autoqa_resultdb_dbschema_4.png]] | |||
Testrun is the common representation of a 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. | |||
=== Idea 1 === | === Idea 1 === | ||
[[Image:autoqa_resultdb_schema.png|1000px]] | [[Image:autoqa_resultdb_schema.png|1000px]] | ||
Revision as of 13:50, 29 March 2010
Result
Testrun is the common representation of a 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.
Idea 1
Idea 2 (UML)
Idea 3 (UML)
