{"id":2439,"date":"2019-07-24T05:47:37","date_gmt":"2019-07-24T05:47:37","guid":{"rendered":"https:\/\/www.folio3.com\/mobile\/?p=2439"},"modified":"2020-03-26T17:12:23","modified_gmt":"2020-03-26T17:12:23","slug":"achieve-test-automation-using-jenkins-ci-tool","status":"publish","type":"post","link":"https:\/\/www.folio3.com\/mobile\/blog\/achieve-test-automation-using-jenkins-ci-tool\/","title":{"rendered":"Achieve Test Automation with Jenkins (CI tool)"},"content":{"rendered":"\n

Continuous integration (CI):<\/em><\/strong> is the Process of automating the code of all developers from multiple working copies into a single software project.<\/em><\/p>\n\n\n\n

Whenever a developer makes a code commit, the software tests the build automatically. For large scalable projects, developers are committing code very frequently, within a day. With each commit, the code is built and tested. If the test is passed, the build is good to go for deployment. This commit, build, test, and deploy is a continuous process and hence the name continuous integration.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Jenkins \u2013 What is this?<\/strong><\/p>\n\n\n\n

It is an open-source Continuous Integration server capable of orchestrating a chain of actions that help to achieve the Continuous Integration process in an automated fashion.
<\/p>\n\n\n\n

Let\u2019s get started.<\/strong>
<\/p>\n\n\n\n

Step 1: Create a test Script on IntelliJ<\/strong>
<\/p>\n\n\n\n

We are using Java as the language and IntelliJ for an IDE. You can use Eclipse as well. We have created a Maven project in which we only have created one test script just for this blog. Once you’re done with the test script do not forget to execute it once.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Note:<\/strong>  <\/strong>If you do not have knowledge of test automation you first need to get it done before jumping in.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Step 2: Create a New Repo on Git<\/strong>
<\/p>\n\n\n\n

Create your account on GitHub and log in. When you log in, you will see an Add New <\/strong>option to create a new repository. Provide a Repo name and select Private or Public for your repo status.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

After creating the repo, you will be redirected to it. Copy browser URL this URL is used in Jenkins and IntelliJ when you push your code.<\/p>\n\n\n\n

Step 3:  Push code on Git Repo<\/strong><\/p>\n\n\n\n

You first have to configure Git on IntelliJ. Follow these steps:
<\/p>\n\n\n\n

In IntelliJ, go inside VCS and select Enable Version Control Integration.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

After this select Git from dropdown.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Now, Go inside VSC and select Commit. A pop up will appear asking you to select a project to commit.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

When you click on Commit<\/strong> button all your project code is pushed toGit.<\/p>\n\n\n\n

Step 4:  Download Jenkins<\/strong><\/p>\n\n\n\n

Hit URL:\u201d https:\/\/jenkins.io\/<\/a>\u201d onto Browser and Select Download button.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

It will show you 2 options for downloading Jenkins, first is the weekly release and the second one is the Long Term Release(LTR). Download LTS as it is supposed to be stable. Therefore, select windows option and Jenkin zip file get downloaded into your system.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Copy zip file and place that anywhere in your system.<\/p>\n\n\n\n

Step 5:  Install Jenkins<\/strong>
<\/p>\n\n\n\n

Follow these steps to install Jenkins through command prompt.<\/p>\n\n\n\n

1.       Open Command Prompt.<\/p>\n\n\n\n

2.       Go inside Jenkins folder.<\/p>\n\n\n\n

3.       Type command: Java -jar Jenkins.war<\/em>
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Click enter, it will take a couple of mins to install. Then you are all set to login into Jenkins.
<\/p>\n\n\n\n

Step 6:  Login into Jenkins<\/strong>
<\/p>\n\n\n\n

Hit URL:\u201d http:\/\/localhost:8080<\/a>\u201d to start Jenkins, it will redirect it to a login page that requires a username and password. Username is \u201cadmin<\/strong>\u201d whereas the password can be used from:
<\/p>\n\n\n\n

C:\\Program Files (x86)\\Jenkins\\secrets\\ initialAdminPassword.txt file<\/em>
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Enter username and password then click on the Sign in button. As you are logging in for the first time, it will ask you to install some plugins.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Click on \u201cSelect plugins to install\u201d then you will be re-directed onto a list of plugins. There are some plugins that already mark for installation.
<\/p>\n\n\n\n

Note:<\/strong> You can install more plugins after setup completion.
<\/p>\n\n\n\n

Step 7:  Started with Jenkins – Setup Job and Manually execute<\/strong>
<\/p>\n\n\n\n

Now Jenkins is finally started and you can see its Home screen in below screenshot.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Let’s get started and set up a task. Click on New Item. It will ask the Name and type of project that you want to create.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Here, I am selecting a Maven Project as I had created a test script in Maven Project inside Intellij and click OK.<\/p>\n\n\n\n

Placing your test scripts on GitHub is always a good approach. I have placed my scripts onto Git.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Back to Jenkins, I mark tick onto GitHub Project checkbox and provide my Git URL in the input box.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

On Scroll down to a page, you will see a section of Source Code Management. Select Git checkbox then you need to provide Git Repository URL and Credentials.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

<\/p>\n\n\n\n

How to Add Credentials?<\/em><\/strong> <\/strong> Click on the Add button for credentials and provide Username and password then click the Add button to submit.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

After you are done with these steps scroll down the page. Now, you need to come inside the Build section and write pom.xml inside Root POM and inside Goals and Options write command: \u201cclean deploy\u201d.
<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Why pom.xml ?<\/strong>   pom.xml is a file that runs all your test scripts defined under it. You do not explicitly need to run each test script you can define all scripts into this file and execute it.
<\/p>\n\n\n\n

Clean Deploy \u2013 What is this ? <\/strong> <\/p>\n\n\n\n

\u00b7         clean<\/strong>: removes files generated at build-time in a project’s directory<\/em> (target by default)<\/p>\n\n\n\n

\u00b7         deploy<\/strong>: copies the final package to the <\/em>remote<\/em><\/strong> repository for sharing with other developers and projects<\/em>.<\/p>\n\n\n\n

Scroll down for some more configuration, you can also configure email Notification that is used when your executed job fails against test script then you will be notified through email notification.<\/p>\n\n\n\n

Before continuing on this, you first need to  email configuration inside Jenkins. Therefore, Click on Manage Jenkins from Home Screen and select Configure System. When scrolling down the page, you will observe Email Notification tab that required some details.
<\/p>\n\n\n\n