Forum Discussion
I am having issues with the License as the error in jenkins is no license found. I am using Ready API 2.0. Can you please provide detailed steps. Much appreciated.
Thanks,
Naga
Whatever user ReadyAPI is licensed to has to be the same user running Jenkins. IE, if you licensed ReadyAPI on your profile, you have to be the user Jenkins runs under.
Otherwise the Jenkins user needs its own license.
- sanj8 years agoSuper Contributor
I had to deal with this recently and yes documentation is not clear on this which is why I outlined step by step how to get jenkins
I do agree with groovyguy both license and jenkins needs to run on the same profile.
jenkins cannot find license server
has all the info you will need to be up and running
- verycoolgreg8 years agoNew Contributor
Also, I have a few tips for all who are trying to run ReadyAPI scripts from Hudson/Jenkins.
In Jenkins, there is an option to produce JUnit type of report.
It comes very handily when we would like to see the results of the test run.
You could also setup Slack (collaboration tool ) with Jenkins and see the test results via slackbot notifications.
Integration of SOAPUI and Hudson/Jenkins
For integration, we have to consider following requirements and same will be used to decide integration style.
Requirements:- SOAPUI should be run from Hudson
- Generate reports in JUnit style and incorporate with Hudson.
- Show logs in console output.
- Run any project with different global properties of SOAPUI
- 1. SOAPUI should be run from Hudson
Hudson have good feature of execution of batch of commands of windows and Linux and SOAPUI is providing test runner of its own, we can run SOAPUI from Hudson easily. We can run it as same way as we can run soapui from command line. So it can be integrated easily and using Hudson we can view console output as well.
For this first create a new job in Hudson. This link will help you understanding the Hudson management; http://www.solitarygeek.com/java/hudson-ci-server-a-step-by-step-guide-part-i/
After creating a job, go to configure section of the job and “Add build step” to run shell script / batch file as below to run SOAPUI from Hudson .- 2. Generate reports in JUnit style and incorporate with Hudson
Hudson have inbuilt functionality of digesting JUnit style report and SOAPUI generates reports in JUnit style and Hudson generates good trending and result reports based on it. To enable JUnit style report in Hudson we have to select “Publish JUnit test result report” option and it will ask for JUnit style report xml file path. If you are creating different JUnit style report in different folder than give that path using wild cards and Hudson will check for all the JUnit style report and will show the consolidated results and trends. The path should be relative to WORKSPACE.
- 3. Show logs in console output
As described in point-1, it is necessary to have log information handy for test and Hudson have special area to show console output.
- 4. Run any project with different global properties of SOAPUI
To make our test dynamic, it is must that our tools supports run time property setup option and SOAPUI command line runner supports this via global properties. Because we can setup global properties values during run time and which we can use to achieve dynamic nature of our test framework and as we know Hudson support execution of tool through command line or shell scripting.
For example, I want to run SOA test daily after nightly build of my application. Here we are assuming that our SOAUI test project is available in SVN and application source is also available in SVN. So for this the steps for setting up job will be as below:- Create one new job in Hudson for building the code.
- Configure SVN from which we have to download the latest source of application.
- Configure build steps like ant script or batch file or shell script.
- Configure schedule to run the job daily.
- Save job.
- Create one more new job in Hudson for testing the build which was setup in previous step.
- Configure SVN path to get latest test project from SVN.
- Configure the batch commands to invoke and run the soapui tests.
- Set build job as triggering job to start this test job.
- Set email address to whom we want to send the test report.
- Save the job.
Now the source build job will start at scheduled time and completion of build it will start the test job.
Conclusion
There are many options in Hudson and SOAPUI to achieve maximum flexibility of building and testing the jobs and apart from this we have integrated functional UI testing with Hudson.- sanj8 years agoSuper Contributor
I am using Junit to publish results did not know about slack
Thats cool
- nagakondapalli8 years agoNew Contributor
The link 'Jenkins cannot find license server' does not work...
Related Content
Recent Discussions
- 4 days ago