Hide Forgot
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 :-)
(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.
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?
will be covered in tcms 4.0.