Report test 'scenario' to ResultsDB
ClosedPublic

Authored by adamwill on Feb 28 2017, 11:05 PM.

Details

Summary

See https://lists.fedoraproject.org/archives/list/resultsdb-users@lists.fedoraproject.org/message/DJSIOLA3YEH6HNSJEXVPLIZT5TW4CDED/
for some discussion of this. To make life easier for consumers
of our results from ResultsDB, we should report the 'scenario'
of the test. This allows consumers to conveniently deduplicate
results: results for the same 'item' and 'scenario' are dupes,
so usually, consumers will only want to consider the most recent
one.

Test Plan

Check the tests pass, report some results to a test
ResultsDB and check the scenario item in the extradata looks
correct.

Diff Detail

Repository
rOPENQA fedora_openqa
Branch
scenario (branched from master)
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 1086
Build 1086: arc lint + arc unit
adamwill retitled this revision from to Report test 'scenario' to ResultsDB.Feb 28 2017, 11:05 PM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jsedlak, jskladan.
jsedlak accepted this revision.Mar 3 2017, 12:00 PM

Code looks OK and if we need it right now, feel free to merge it, but I wonder how will the discussion evolve.

This revision is now accepted and ready to land.Mar 3 2017, 12:00 PM

I think we're OK to go with this for now, too, at least if I'm reading @kparal correctly - if anything, his remaining question is whether the test name should be in the scenario. But even if we decided to take it out in future, I don't think that's a problem, intended usages wouldn't be affected by the change I don't think. So I'm gonna go ahead and merge this.

adamwill closed this revision.Mar 3 2017, 11:59 PM