Hi Mike,
Step 1 to 3 are to test 1st role of the function X times (with different param), Step 4 top 6 are to test the 2th role of the function X times and step 7 to 10 are to test the last role of the function X times.
If I understood you correct here, each invocation of the 'X-times' invocation potentially takes different parameters, right? So what you are trying to achieve is:
do role 1 with param a, b
do role 1 with param c, d
do role 1 with param e, f
do role 2 with param g,h ...
Is this correct?
So using a solution for KLAROS-271 you would create a test case as following:
1. test step description: For the following actions use parameters: a, b
2. test fragment reference (a predefined set of test steps describing the actions for a role 1 invocation)
3. test step description: For the following actions use parameters: c, d
4. test fragment reference (same as above)
5. test step description: For the following actions use parameters: e, f
6. test fragment reference (same as above)
7. test step description: For the following actions use parameters: g, h
8. test fragment reference (a predefined set of test steps describing the actions for a role 2 invocation)
So beside the test case you will have to create fragments for each role once and include those.
Is this something that would solve your problems?
Of course I can change the dénomination and create a test cases for each role of a Functions.
Actually I think this is the clearer solution. While currently test suites are 'flat' In a way that they can only contain test cases, this will change in future versions, where test suites will be nestable.
Regards,
Torsten