Continuous test execution is an essential part of automation testing, especially in regression run. If you need to start execution manually means your return on investment is not as good as needed. There are multiple ways to do this. Developers in many companies use Continuous Integration (CI) tool like Hudson, Rational Team Concert for building application multiple times in a day where codes are checked in from multiple locations. You can use the same feature of building application to perform testing as well. You can build your own in-house application to perform the same task. I will give an idea for the same at the end of the blog.
I use WebDriver for automation testing in .NET framework. I heard that many companies use Jenkins for CI and even for testing so thought to implement my tests written in C#. After some research on the internet, I was able to implement a basic skeleton for continuous testing. In order to understand and to customize Jenkins, we will go Step by Step.
- Download Jenkins.
- Run and verify Jenkins.
- Install as a Window Service.
- Configure Jenkins as a slave. (Optional. Read only if you want to learn.)
- Create Job to execute the test.
1. Download Jenkins:
In order to download Jenkins, Go to http://jenkins-ci.org/ and download ‘Latest and greatest’ version of Java web archive (.war) file and save it to some location.
2. Run And Verify Jenkins:
Open Command window and navigate to the location where you have downloaded *.war file. Execute following command (I saved Jenkins.war file in D drive)
You will see following output
If you read all lines you will see that HTTP Listeners started at port 8080.
3. Install Jenkins as Window Service:
Node: If you install as window service, your tests will run in the background.
Perform Step 2 if not yet done. Click ‘Manage Jenkins’ you will see the following screen with various option.
Click on ‘Install as Windows Service link. You will see the following screen.
Click on Install button. Once installation complete you will see following:
Go to Window Services and verify if you can see there or not. For now, you will not require starting Jenkins site on the command line. You can directly start http://localhost:8080/ if your Jenkins service is running. NOTE: if you are using only window OS then you can directly install native package from http://jenkins-ci.org/ You need to unzip the folder and install MSI file. That will install and get ready for step 3.
4. Configure Jenkins as a Slave:
This is most interesting part of Jenkins. Here you can configure your slave attached to Master which is ready for step 3. You can assign tasks to various slave to perform like test execution etc. Start Jenkins Website and click on the link ‘Manage Jenkins’. You will see following option among various other options. Click on the above option which will take you to the following screen. Now you need to create Node that connected to master (Just like GRID (HUB-NODE)). To do that you need to click on ‘New Node’ link that should you to following screen. Give some Name of Node and Click on Dumb Slave radio button that will activate the OK button. Click on OK button. This will take you to the following screen. You can click on Help icon to understand more about the fields. I am giving following options # of executor: 1, Remote FS root: D:\Shared. Launch method: Save this. It will take you the following screen. As you can see above, you can start that node by given three options. It is up to you, to choose but I prefer the first option. Click on the Orange button with Launch. This will ask you to download slave-agent.jnlp. Please save this to the location where you have created your slave i.e. D:\Slave. Open command prompt and change directory to the location where you have saved this file and execute following command Javaws slave-agent.jnlp after some processing you may see following windows: This will disappear in few seconds and you will see Jenkins slave Agent screen with ‘Connected’ text on the screen. If you go back to Jenkin site and refresh the page in Manage Node screen, you will see the following screen. You can install this slave into the machine as window services using File menu given in ‘Jenkin salve agent’ screen so in future you will not require doing the whole process of starting slave via jlnp Click ‘OK’. This may ask your permission to run the program. Will see that Jenkins slave agent window disappear and if you check in ‘services’ you will be able to see slave as services. Go back to Jenkins site and Click on slave link the page and make sure that you can see slave running. Now your slave is connected to your master and ready to serve you for execution by added execution job assigned by you as given in next section.
5. Create JOB to Execute Test:
Once your slave node is running, go to home page of Jenkins and click on ‘New Job’. This will take you to the following window. Provide Job name as per your choice and select radio button. ‘Build a free-style software project’. And hit OK.
This will take you the detailed screen and you can fill information as you needed. Few points are very important which you should consider.
- Execute test at specific Node.
2. Regression Run repletion :
How frequent you want to execute the test.
There are various commands you can give to select the frequency of test execution ie. Every hour or at every day at some specific time frame. You can Google the commands or I can write a separate article about this if needed.
3. Execute Tests from various options (batch command preferred at least in my case)
4. Post Execution:
Configure to send email or prepare report as NUnit/Junit repot etc.
Once you save this job this will take you to the following screen.
Click on [Back to Dashboard] link that will take you the following screen.
To execute test you can click on. You will see the following screen.
I think much detail covers the basic understanding of Jenkins configuration for test execution. I hope this will give you are the direction to configure Jenkins in your project. I use Webdriver in .NET environment and configure Jenkins for continuous execution and it was successful implementation but later we decided to build our own internal application to specific for our own application which can do continuous execution and other tasks as well which is not possible via Jenkins like customized internal website with customized graph and tables but that’s another story.
I am going to write another article specifically how to execute tests using MSBuild, msTest and Nunit and another article for JUnit.