Forum Discussion
thowo
New 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
richie
4 years agoCommunity Hero
Hey 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
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
- 11 months agosinis
Recent Discussions
- 2 days agoruchisingh