| << Back to previous view |
|
[QB-833] repeat parameter excludes duplicates
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.1.17 |
| Fix Version/s: | 3.1.22 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Rafal Krzysztoforski | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
for repeat parameter of a step (included in parallel composition step) I set up a param with comma separated values:
1,2,3,4,5,6,7,8,9,9,10,11,12,13,14,15,16,17,18,19,20,40,40 the QB run the step in parallel but it excluded redundant values: 9 and 40 |
| Comments |
| Comment by Robin Shen [ 25/Feb/11 12:42 PM ] |
| Since the param values will be used to identify step instances, they can not loop against a same set of value. A workaround is to use some suffixes to distinguish them, for example, define them as 40.1, 40.2. |
| Comment by Rafal Krzysztoforski [ 25/Feb/11 01:45 PM ] |
|
Why QB cannot use to identify step instances an internal prefix created by QB?? Why it interprets user parameters excluding values which can be automatic values (if taken from file)?
Value of a parameter is a just a value - QB should stay away from modifying the list. |
| Comment by Rafal Krzysztoforski [ 25/Feb/11 02:47 PM ] |
|
For additional investigation please consider following example.
Step is triggering a test cmd /c execute.cmd PARAM repeat parameter is: PARAM values 1,2,1,2,3,4 (random values generated for tests) with your suggestion i'm forced to use additional logic inside my script to be able to detect test reruns please review this issue again |
| Comment by Robin Shen [ 26/Feb/11 01:01 AM ] |
| What you described does make sense. I will investigate this issue again to see if QB can generate some internal ids to distinguish identical param values. |