AutoQA resultsdb schema

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Result)
Line 3: Line 3:
 
[[Image:Autoqa_resultdb_dbschema_4.png]]
 
[[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).
+
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

Contents

Result

Autoqa resultdb dbschema 4.png

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

Autoqa resultdb schema.png

Idea 2 (UML)

Autoqa resultdb schema2.png

Idea 3 (UML)

Autoqa resultdb schema3.png