|
2015-09-25
| ||
| 09:54 | • Closed ticket [316c0bdb7b]: jobgroups behavior in testconfig plus 3 other changes artifact: 9997c24015 user: tyardeni | |
|
2015-09-24
| ||
| 14:12 | • Ticket [316c0bdb7b]: 5 changes artifact: be380a0d85 user: tyardeni | |
| 14:09 | • New ticket [316c0bdb7b]. artifact: f0e06c1808 user: tyardeni | |
| Ticket Hash: | 316c0bdb7b886f5af7622cd0669283c2bff2e4a7 | |||
| Title: | jobgroups behavior in testconfig | |||
| Status: | Closed | Type: | Feature_Request | |
| Severity: | Important | Priority: | Immediate | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2015-09-25 09:54:13 | |||
| Version Found In: | ||||
| Description: | ||||
| I would like to request an enhancement to how jobgroups are handled within the testconfig. The level of control for an itemized test needs to be at the item level. | ||||
| User Comments: | ||||
|
tyardeni added on 2015-09-24 20:12:42:
The behavior I would like to see in testconfig is as follows. Given the following item definition: [items] ITEM_LVL1 block ITEM_LVL2 param I would like a [jobgroups] block that has visibility to the variables defined in [items]:
[jobgroup]
default #{getenv ITEM_LVL1}
This is scalable for defining multiple jobgroups for a test. tyardeni added on 2015-09-25 15:54:13: Closing duplicate | ||||