From Fedora Project Wiki
No edit summary |
(→Result) |
||
| Line 3: | Line 3: | ||
[[Image:Autoqa_resultdb_dbschema_4.png]] | [[Image:Autoqa_resultdb_dbschema_4.png]] | ||
Testrun is the | 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). | 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). | ||
Revision as of 13:51, 29 March 2010
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).
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)
