Forum Discussion

yahiatene's avatar
yahiatene
Occasional Contributor
6 years ago

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 : ...
Automation Environments
ci
Health-check
Jenkins
Pipeline
SOAP
  • cambiatihealths's avatar
    cambiatihealths
    28 days ago

    Hello Mohamed,

    Ensuring a robust health-check routine for ReadyAPI and SoapUI Pro in your CI pipeline is crucial for seamless operations. Here are some best practices:

    1. TestRunner Availability: Use a simple script or API call to verify the TestRunner's presence on the expected path before starting the CI. This ensures the tool is correctly installed and accessible.
    2. License Verification: Implement a script to check license availability. For floating licenses, the license server’s status can usually be checked via its management interface or an API.
    3. Component Readiness: Running a "blank test" is a good starting point to ensure all components (TestRunner, Test Cases, Data Sources) load without errors. For a stricter check, execute a lightweight mock test or a dry run to confirm all integrations are functioning.
    4. Automated Health Checks: You can script these checks and incorporate them as a pre-stage in your Jenkins pipeline to avoid manual intervention.

    ReadyAPI does not have an out-of-the-box health-check routine, so scripting these verifications is key. Let me know if you'd like examples of these scripts!

SiKing's avatar
SiKing
Community Expert

I am unclear what exactly you are trying to accomplish.

 

yahiatene wrote:

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

Could you give an example of such a tool?

 

yahiatene wrote:

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

What would you expect to happen in your pipeline if any of the above fails? And perhaps more importantly: What would expect different from just failing your test run?

 

yahiatene wrote:

So the point is :

  • - What are the best-practices you have observed in IC integration ? What is your advice ?

What I have always done is to keep integration tests in a separate project (both in CMS as well as in CI), chain the projects together, and fail that project run if anything goes wrong. When the project fails, a human is going to have go and investigate, regardless of the failure.

yahiatene's avatar
yahiatene
Occasional Contributor
6 years ago

Hi SiKing,
Thank you for your reply, I'll try to be more clear.

SiKing wrote:

I am unclear what exactly you are trying to accomplish.

 

yahiatene wrote:

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

Could you give an example of such a tool?

For example I worked with Jira and HPQC, with both of them we can check their availability and status with some HTTP requests.

 

yahiatene wrote:

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

What would you expect to happen in your pipeline if any of the above fails? And perhaps more importantly: What would expect different from just failing your test run?

 

What I'm trying to do is a model pipeline to launch fake (blank) tests to see the status of readyAPI and it's License Manager.
For example : if the quantity of licences is insufficient to run the job, the pipeline fails and sends an email to our Tools Expert to check which jobs are using all the licenses. Today we have the console output "No valid license found" just when it fails, and if it's possible we want to have :
4 floating licences found
2 used licenses
2 free licences  

 

yahiatene wrote:

So the point is :

  • - What are the best-practices you have observed in IC integration ? What is your advice ?

What I have always done is to keep integration tests in a separate project (both in CMS as well as in CI), chain the projects together, and fail that project run if anything goes wrong. When the project fails, a human is going to have go and investigate, regardless of the failure.

So the goal is to make model pipeline, to automate it's run and to do it before production pipeline run.

Best regards,
Mohamed.