Bug 838479

Summary:	[RFE] Test version should be printed in protocol in journal
Product:	[Fedora] Fedora	Reporter:	Zbysek MRAZ <zmraz>
Component:	beakerlib	Assignee:	Dalibor Pospíšil <dapospis>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	amarecek, azelinka, ebenes, jjaburek, pmuller, psplicha
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-02 14:07:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zbysek MRAZ 2012-07-09 08:39:51 UTC

When reviewing tests results, you are not able to see version of the test which was used.

The test protocol in testout.log should print with the duration time, architecture, hostname and other informations also the version of the test.

Comment 1 Jiri Jaburek 2012-07-09 13:24:53 UTC

Note that "test version" here probably refers to beaker RPM version of the test / git tag name rather than TESTVERSION exported in Makefile of each test.

Comment 2 Petr Muller 2012-07-09 14:18:12 UTC

I'll need to think about that: the test version is Beaker specific thing, therefore not a real upstream material. But the modifcation is probably needed to go into the journal, and I cannot do that in beakerlib-redhat. I'll probably just patch it in the RPMs going to Beaker.

Comment 3 Aleš Mareček 2013-02-20 15:15:17 UTC

Is it possible to call some function (from beakerlib-redhat) that can do the job? The function could be listed automatically by beaker-wizard.

(I don't know if this is possible, just my 2 cents...)

Comment 5 Fedora Admin XMLRPC Client 2014-09-02 12:13:30 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Dalibor Pospíšil 2014-09-02 14:07:10 UTC

If the test is executed in beaker the test version can be obtained from beaker logs. If it is execute elsewhere it is nearly impossible to get the version as the source of the test can be various. The only think I can imagine is to have some functions which would call some registered callback function/program which provides desired info in specific environments. If something like this is needed feel free to reopen this bug.