[JBEHAVE-527] Composed steps not being matched when using non-named parameter matching for the composite step - jira.codehaus.org

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 3.4, 3.4.1
Fix Version/s: 3.4.2, 3.5
Component/s: None
Labels:
None
Environment:

Hide
After the introduction of the specifications of parameters as meta (~~JBEHAVE-487~~) the composed steps are not being matched if meta parameters are specified as they superseed the parameters specified in the composite step.

Need to merge the two set of parameters rather than choosing one over the other.

Show
After the introduction of the specifications of parameters as meta ( JBEHAVE-487 ) the composed steps are not being matched if meta parameters are specified as they superseed the parameters specified in the composite step. Need to merge the two set of parameters rather than choosing one over the other.

Mauro Talevi made changes - 04/Jun/11 3:37 AM

Field	Original Value	New Value
Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]

Mauro Talevi made changes - 08/Jun/11 3:38 AM

Fix Version/s

3.5 [ 17393 ]