Bug 863434

Summary:	[RFE] Better support for single test case in multiple setups
Product:	[Other] TCMS	Reporter:	Frantisek Reznicek <freznice>
Component:	Application	Assignee:	Yuguang Wang <yuwang>
Status:	NEW ---	QA Contact:	Nobody <nobody>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.0	CC:	dahorak, junzhang, ltoscano, ryang, vchen
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Frantisek Reznicek 2012-10-05 13:21:42 UTC

Description of problem:

As we test layered product we have tests which can be ran under different conditions (called configurations).
Talking in concrete example:
 A] Let's have simple client - server scenario and test does message transmit and reception & check of correctness and check of timing

This simple test scenario can be run on
 a] standalone server
 b] clustered server (openais/corosync)
 c] RHCS clustered server (cman)

Those points show simple testing scenario A] in three different configurations / environments (setups) a], b], c].

We are having typically around 10 different setups for simple test scenario.
TCMS / Nitrate should much better support this structure.

In my view TCMS / Nitrate should introduce Setup, Breakdown, Actions, Expected Results objects and allow creation of new test case based on creation new or selection existing (Setup, Breakdown, Actions, Expected Results) objects.

Proposed change has significant impact on Nitrate xml-rpc API as well.

This change will allow to automate TCMS test case creation for self-documented tests (bug 843823)

Version-Release number of selected component (if applicable):
N/A

How reproducible:
N/A

Steps to Reproduce:
N/A
  
Actual results:
Weak support of single test scenario ran in different setups / configurations.

Nowadays there are at least two approaches:
a] test cases copied and part of the setup modified - testing scenario duplicated and if changed then not easy to sync the testing scenario among all of the copies.

b] use of template test plans
  1] creation of template setup plans (just setup field filled)
  2] creation of template actions and expected results plans (just ctions and expected results filled)
  3] creation of set of test cases with links to 1] and 2] in their setup / action&expected results fields
  This workarounds the problem, but 'template plans' are not having runs, might be confusing and waste TCMS test plan resources.


Expected results:
Better support of single test scenario ran in different setups / configurations.

Additional info: