cancel
Showing results for 
Search instead for 
Did you mean: 

Health-check for SOAP UI Pro in continuous integration with Jenkins

Highlighted
Occasional Visitor

Health-check for SOAP UI Pro in continuous integration with Jenkins

Hello,
Most of tools dispose of “health check” routine that verify that everything is OK before starting the CI pipeline.

So before executing the SoapUI tests in Jenkins I want to verify that :

  1. - TestRunner of ReadyAPI is available
  2. - Licences are available in sufficient quantity
  3. - Each component  of the testing tool is ready to use

Maybe it is very simple and I just have to run a blanc test, maybe the control is stricter and I can run some of health-check procedure.

 

So the point is :

  • - What are the best-practices you have observed in IC integration ? What is your advice ?
  • - Does the health-check procedure exists and how to run it ?

 

Thanks a lot Smiley Happy 

Mohamed.

3 REPLIES 3
Community Manager

Re: Health-check for SOAP UI Pro in continuous integration with Jenkins

Community, is there anything you can suggest? @nmrao@msiadak, @Radford@avidCoder?

 

 

 
---------
Tanya Gorbunova
SmartBear Community Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.↓↓↓↓↓
Community Hero

Re: Health-check for SOAP UI Pro in continuous integration with Jenkins

Based on my experience with Jenkins and pipelines with ReadyAPI so far, there's no easy way to do what you are asking. You basically want to do a health check on ReadyAPI, but as far as I am aware there's no out-of-the-box solution to do that. You mentioned the idea of running a blanc test, which is likely an easy solution to start with that you can refine as you go.




---

Click the Accept as Solution button if my answer has helped, and remember to give kudos where appropriate too!
Community Hero

Re: Health-check for SOAP UI Pro in continuous integration with Jenkins

@yahiatene 

 

While I agree with @msiadak , following are my remarks.

In the pre-build step, try the following

1.  testrunner is a file after all. You can can check it exists

2. Depends on the type of the licence. If it is fix type assigned to (which is the preferred type at least for CI builds) jenkins machine, no need to bother about it. It will be problem only if you are using floating licence and some other guy in the team is using it.

3. I think you may use some  plugin  so that call http request (for the application under test) as part of pre-build step for the endpoint and see if that is giving 200 OK.



Regards,
Rao.
New Here?
Join us and watch the welcome video:
Top Kudoed Authors