Forum Discussion
I tried before and it wasn' t working for me.
Now i don't know if there is update about this.
- richie4 years agoCommunity Hero
Hey thowo
Exactly how are you running the testRunner?
Are you just talking about executing the project in a headless mode or are you talking about running it from a CI/CD/CT environment?
What sort of project is it? Is it a composite project or a flat .xml project?
You have to be careful when creating a project in ReadyAPI! that is going to be/could be executed from within opensource SoapUI because within the project you can't use pro/ReadyAPI! functionality wihtin the project - stuff like the data driven functionality, event handlers, etc.
As long as your ReadyAP! project doesn't include this functionality, you should be able to open the project in SoapUI and execute the tests, whether via headless/commandline testRunner or via the GUI mode - i did this 2 years ago and it worked then.
HOWEVER - opensource SoapUI doesn't support composite (unflattened) ReadyAPI! project files. The project files need to be of the flat .xml type before SoapUI can deal with it, but if you've converted your ReadyAPI! project to the composite option, this won't work.
ta
rich
- thowo4 years agoNew Contributor
Hi rich,
Thanks for your quick reply.
The testRunner runs in the open source version on a Linux server. It is correct that the project is running there in headless mode.
We are not currently using the ReadyAPI-test. It is a SoapUI open source project. We are now considering having ReadyAPI supporting the development, but would like to work with the open source testRunner on the various test servers. Then we would only need a ReadyAPI license or two for development.
In the case of the project, we are more concerned with the more comfortable operation under ReadyAPI than the extended functions. So we would have to get there with the flat XMLs.
Best regards
Thomas- richie4 years agoCommunity HeroHey thowo,
So youre running it via a CI/CD/CT environment, so this complicates things a little.
I'm curious, from what you've said id suggest there's some difference in the content of the project .xml files between the soapui vs readyapi! versions.
What i suggest to help diagnose the issue:
Create a new soapui project containing a single testStep (single executable teststep), in a single testCase in a single testSuite.
Create an equivalent readyapi! project.
Attempt to run both via testRunner and monitor the logging and compare and contrast the results.
Ta
Rich
Related Content
- 4 years ago
- 2 years ago
Recent Discussions
- 21 hours ago
- 3 days ago