soapUI Pro 5.1.0

Hi,

I suppose you have a composite project in the workspace and we have redesigned our composite project so it creates a new folder for composite project.

Thanks,
Jeshtha

Are these new style projects backward compatible?

Hi

I can't find any information about the new folder change. What is it doing, and why is there a GUID on the end?

Is it something to deal with renaming test suites (which used to create a new folder)?

Hi,

@Liberty Information Technology Support, the new format is not backward compatible.
Once the conversion occurs, you should stay on 5.1 or if you have to, make sure to not save the project in an older version.

gordonb Your original composite project folder with remain intact, but one with _new suffix will be created. The changes address some duplication issues that could be encountered in the previous format.

Regards,

Giscard
SmartBear Support

Hi,

I just tried to converted new project format and found some test case files hit the limitation of maximum length of file name by Windows file system.
After that, I cannot delete the test cases.

Is there any workaround?

this is not an acceptable work around.
I am using svn to version the composite project (which is already not easy).
But changing all the file and project name totally screw this up.

You should think of a better way to have a configuration file that does not depend of the filename.
Also, you should not save the test case results in the configuration file but instead you should have a result.xml file independant

Anyway I can't upgrade to the next version.

I have composite projects setup in my workspace and I am encountering the same problems and more:

1. Hitting windows file path limits
2. SoapUI does not copy over non-source files (.xls data source files for instance) to the new composite folders.
3. Any attempt to re-locate data sources to reside outside of the composite project (a measure taken to prevent future issues like this) results in an error: Unexpected record type (org.apache.poi.hssf.record.StringRecord)

Not to mention the headache of having to incorporate changes to file names and folder structure into my source repository.

Any assistance in resolving my issues would be appreciated. In the meantime I will remain with 5.0.0

kevman fderunes
We have logged the issues you have raised.

Tal - AUS Support likewise, but note that external files like DataSources were not previously put into the composite project folder.
You still referenced them from their respective locations after converting a simple project to composite.
I point 2, you said the files were not inside the composite project folder, but in point 3 you are moving them out. Please clarify what you were trying to do and your concern also about the external files.

Regards,

Giscard
SmartBear Support

Anonymous Support,

Data sources were in my original composite folder. I put them there. In hindsight, not a good idea. With the creation of the "_new" composite folder I tried to move the data sources into that folder but encountered issues with windows file path limits. My subsequent attempt to then move them to a "Common" data sources folder outside of the composite folder (i.e. where windows file path limits won't be encountered and to prevent issues like this in the future) failed with the error previously noted, "org.apache.poi.hssf.record.StringRecord". I will this try again, maybe just an anomaly.

Also, you stated the following: "Your original composite project folder with remain intact, but one with _new suffix will be created"

From the above comment, you are not suggesting the original composite folder be retained, right?

Regards,
Daniel.

There is definitely an issue with DataSources albeit just for my composite projects. Steps I have taken so far:

1. Opened the 5.0.0 workspace in 5.1.0
2. Clicked OK to update the Composite projects.
3. Opened a testcase in the ValidationService-soapui-project_new project with an excel DataSource and confirmed the path to the excel spreadsheet was still correct: "${projectDir}/ValidationService-soapui-project/TestSuiteValidationService/DataSource/DataSource-ValidationService.xls"
4. Attempted to run the DataSource to return 10 rows but no rows returned.
5. Attempted to run the testcase and received the following message for the DataSource Test step "Missing property values in DataSource Row"
6. I then changed the path to be an absolute path and attempted steps 4 and 5 again but again nothing is returned

I then created a brand new workspace with a new composite project referencing the same validation service and having a DataSource step pointing to the same excel spreadsheet in SoapUI 5.0.0 then opened it in 5.1.0 and it worked with no issues.

So clearly there is something about my composite projects that are causing issues.


Edit: I've figured it out! Excel Data Sources with 35 or more properties stops working!