Forum Discussion

Liberty_Informa's avatar
Liberty_Informa
Regular Contributor
12 years ago

[Registred] Duplicate TestCase Name

Hi

I think this is a serious defect in the soapUI tool. In soapUI you can create duplicate testcase, which should not happen in the ideal world.

Follow the steps.

1. Import WSDL
2. Create soapUI Project
3. Create TestSuite
TestSuite is created with all operations from the interface

4. Again click on Interface and say 'Generate TestSuite'
5. This time select previously generated testSuite
6. Deselect all the operations and select merely one operation for demo
7. Click OK. You can see duplicate testcase is created.

Refer attachment.




I think how it should work is, when user selects previously generated testsuite, soapUI should only display those operations which have not been added to the testSuite.

I hope you understood the problem.

I am using soapUI Pro 4.5.1 on Windows 7.

Thanks
  • Hi,

    I was able to reproduce what you are saying, but I don't understand why someone would need to generate a testsuite and select a previously created test suite and then select operations that already exist in the previously created testsuite. If you don't want operations that already exist in the testsuite then don't select them.


    If there is something I'm missing then please clarify further.


    Thanks,
    Marcus
    SmartBear Support
  • Liberty_Informa's avatar
    Liberty_Informa
    Regular Contributor
    Imagine there are 50 operations on the interface and testsuite has been created with those initial 50 operations. In typical SOA environment many new operations are constructed as part of the business deliveries. Now consider 12 new operations have been added to the same interface. So the total count of operations is 62.

    If I update the interface today, and wanted to add delta 12 operations to the testsuite, tell me what is the best way to achieve this in the soapUI in a user friendly manner?

    Thanks.
  • Hi,

    I see what you are saying. There should be a filter of some kind to not add requests that are already there. I believe this should be an enhancement request than a bug though.



    Regards,
    Marcus
    SmartBear Support