Forum Discussion

Keba_Inc__Suppo's avatar
11 years ago

Composite project: Problems with saving projects.

Hi,

I'm currently testing the functionality of coposite projects when working from 2 different workstations and I have 2 problems with it:

1. Saving issues due to overwritten files
Following scenario:


  • I have a project with 1 suite with 2 test cases.

  • Workstation 1 adds a step to test case 1

  • Workstation 2 adds a step to test case 2

  • Workstation 1 saves.
    --> OK: Only "element.order" and the file of test case 1 are changed and saved.

  • Workstation 2 saves.
    --> NOT OK: For some reason SoapUI tries to save "element.order" and both test case files, even though this workstation has only changed test case 2.

The result is that workstation 2 gets asked if the file for test case 1 should be overwritten, which in my eyes is wrong. If user 2 does confirm, the changes of workstation 1 are reverted.

Is this a known bug? Or is there something I can do to avoid this behaviour?
(I use SoapUI Pro 5.1.2.)

2. Overwriting message only with test case id
Everytime I get the message that a file has been modified externally, the message only states the Id of the changed item, which for the user is rather useless. an example:
"File for [ea52fedb-a4e0-4a7b-ba85-bf0dc1888389] has been modified externally, overwrite?"

Is this normal? Shouldn't there be something like the test case name?


best regards,
Michael
  • Hi,

    That does not sound like normal behavior. Is the composite projects being used on a shared directory? Was this composite project originally created with SoapUI Pro 5.1.2?


    Regards,
    Marcus
    SmartBear Support
  • Hi,

     

    I noticed that the overwriting message still shows the id. Is this a defect or normal functionality.

    I've installed the ReadyAPI-x64-1.5.0-m-SNAPSHOT on 17 December 2015

     

    The version we where using was SoapUI Pro 4.6.4 which shows the names of the files.

     

     

    Best regards,

     

    Mark