Clone TestStep naming defect
There is a minor problem with the cloning process and TestSteps with the exact same name can be created. This was done in soapUI Pro 3.0 beta one, nightly build from 06/03/2009.
Steps to reproduce:
1) Have a least a couple of test steps (I'll call them TestStepA and TestStepB)
2) Clone TestStepA
3) On the rename step, give it TestStepA
4) Note that you are prompted to give the TestStep a unique name
5) Click Cancel
6) Note that no new TestStep is created (as expected)
7) Clone TestStepB
8 ) Name it TestStepC and click OK to create the clone
9) Note that TestStepC appears (as expected)
10) Drag and drop TestStepC to a new position
11) Note that TestStepC is now called TestStepA (and now you have two of them)
12) Open the editor for TestStepC (now called TestStepA) and note that it is indeed a clone of TestStepB
13) Save and close soapUI Pro
14) Upon relaunching soapUI Pro and opening that project, you'll be prompted to save the TestStep with a unique name
It appears that at some point with the move, the previously stored name gets used to name the TestStep.
Steps to reproduce:
1) Have a least a couple of test steps (I'll call them TestStepA and TestStepB)
2) Clone TestStepA
3) On the rename step, give it TestStepA
4) Note that you are prompted to give the TestStep a unique name
5) Click Cancel
6) Note that no new TestStep is created (as expected)
7) Clone TestStepB
8 ) Name it TestStepC and click OK to create the clone
9) Note that TestStepC appears (as expected)
10) Drag and drop TestStepC to a new position
11) Note that TestStepC is now called TestStepA (and now you have two of them)
12) Open the editor for TestStepC (now called TestStepA) and note that it is indeed a clone of TestStepB
13) Save and close soapUI Pro
14) Upon relaunching soapUI Pro and opening that project, you'll be prompted to save the TestStep with a unique name
It appears that at some point with the move, the previously stored name gets used to name the TestStep.
