Bug 767637

Summary:	Tracking tree (compose) quality in TCMS
Product:	[Other] TCMS	Reporter:	David Kovalsky <dkovalsk>
Component:	Application	Assignee:	Yang Ren <ryang>
Status:	NEW ---	QA Contact:	Nobody <nobody>
Severity:	high	Docs Contact:
Priority:	high
Version:	Devel	CC:	azelinka, benl, junzhang, mganisin, ryang, vchen
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	4.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	768041
Bug Blocks:	593666

Description David Kovalsky 2011-12-14 15:18:30 UTC

Up to this date, we don't have a good tool to track which composes (trees) are dead on arrival [DOA], are installable, qualified by Release Test Team and generally good for testing. 

I believe this information belongs into TCMS, so far we've been using a combination of Beaker flags and a set of wikis. It's not necessary to say it doesn't scale well across the company size of Red Hat. 


I'd like to suggest this for TCMS 4.0 Development, if we can use this for RHEL7 - that would be great. 


CCing Marian Ganisin from Release Test Team who always has good ideas to share :-)

Comment 1 Marian Ganisin 2011-12-15 16:00:39 UTC

(In reply to comment #0)
> CCing Marian Ganisin from Release Test Team who always has good ideas to share
> :-)

:) I am not convinced that this statement is correct, anyway I really have some idea.

Here is some real story:
RHEL 6 has several variant for several architectures. There is Server for example, this passes all test and is accepted for testing. However variant ComputeNode is not installable because of some missing dependencies.
Now we have to report this information to stakeholders.

Actually I reported 2 additional bugs. These RFE bugreports are based on our workflow and they should significantly change/improve reporting:

Bug 768036 - RFE: Test Run needs Pass/Fail result field
Bug 768041 - RFE: New view: Test Run Sets

With these features implemented we will be able to report efficiently information described in initial description.

Currently we create test run for every particular combination of architecture and distribution variant and these runs don't hold information if testing passed or not. We have to track this on wiki and in emails. We have to also group these particular runs in some reasonable form.

With those improvements we will be able to provide something like this:

 - Every test run for each particular architecture / variant will clearly state if it is ready for testing.
 - All the information will be easily accessible on one place.
 - and available directly in TCMS.

Comment 2 David Kovalsky 2012-03-13 16:33:47 UTC

Hi guys, 

is this on the roadmap for version 4.0? 


More generally speaking - do you have a tracker for bugs / features for version 4.0?

Comment 3 yawei Li 2012-05-18 02:46:19 UTC

will be covered in tcms 4.0.