Jenkins Pipeline Setup for Test Automation

Hope you guys are doing good. This is a small bit of my experiences while configuring test automation with continuous integration.

Initial need :


My need was to find a way to run a 
  • Performance Test (Jmeter)
  • UI automation Test (Robot)
  • Send an Email
As a solution, I used Jenkins Pipeline to achieve my goal. There might be a lot of other areas that you can use, but with some simple, common methods you can build a Jenkins pipeline script.


These are the pipeline concepts that I have used

Node :

A node is a machine which is part of the Jenkins environment and is capable of executing a Pipeline.

Stage :

A Stage block defines a conceptually distinct subset of tasks performed through the entire Pipeline (e.g. "Build", "Test" and "Deploy" stages), which is used by many plugins to visualize or present Jenkins Pipeline status/progress.

Dir(<Your directroy>){} :

Specifying a directory that you want to execute a specific task

P.s There are many other concepts like Step, etc. I did not use them

For the Local Jenkins Config, My Pipeline script is planned like this.

 node{

    stage('This Stage will execute the Performance Test and Publish The Report')
        dir(""){
            bat 'jmeter -Jjmeter.save.saveservice.output_format=xml  -n -t <JmeterFile>.jmx  -l  <ReportLocation>.jtl' 
            perfReport  sourceDataFiles: '<ReportLocation>.jtl', compareBuildPrevious: true
    }

    stage('This will run the Robot Framework Test'){
        dir("Robot Test Automation Directroy") {
             bat 'robot <Robot Script>.robot'
        }

        }

    stage('Email Test'){
            emailext attachmentsPattern: dir("<Attach Folder Path>"){"**/*"} ,
            body: '<Body Test>', 
            subject: '<Subject>', 
            to: '<To Email>'

        }

   }
bat command is used since I'm using Windows. If you are using Linux, you need to go with Sh

 The main structure you need to understand in the pipeline is

 node{
stage('Name of the Stage'){

 <Code to Execute>

 }

 stage('Name of the Stage'){

 <Code to Execute>

 }

 }

 You can define as much as stages you need. If a stage failed in the middle the build will fail without moving to other stages. If you need it to continue if a stage in the middle got failed, you need to use 'try catch' in the node script.


For more information about the pipeline concept refer to this link: https://jenkins.io/doc/book/pipeline/

Comments

Post a Comment

Popular posts from this blog

QA Engineering Performance Analysis: Don’t underestimate the power of the 99th percentile

Image
If you are in the software development or software quality assurance stream, one of the most important facts for you is the performance (The performance of your application). Simply you want your application to run smoothly with an increased amount of a practical load. In order to measure the possibility, you are probably using different tools and methods in the industry. It’s true the tools will get your inputs and give you some results. But still we have a problem in analysing the data to get an idea about our systems performance. Let’s assume you decided to test your systems performance using Jmeter (Find more about Jmeter If you are not aware about it -  https://jmeter.apache.org / ). Then you’ll run some tests and get some stats about your system. If you are a newbie you’ll probably think about the Average response time and sometimes you might feel confident after seeing the results. The problem is, although you have a set of positive proof of saying the system runs smooth
Read more

Test Automation With Robot Framework

Image
Robot Framework Basics When it comes to "Test automation" there are a lot of tools and technologies to be found in the industry. For example, there are tools and frameworks like TestNG, JMeter, Katalan Studio, HP Test Suite and Robot Framework, Cucumber etc. Today I'm planning to speak about the Robot Framework, which is a python based test automation tool. What's special about this framework is the simplicity of the test script that we have to write. If you are familiar with cucumber It's somewhat similar to that. In another way, we can say scripting in robot framework is as simple as using predefined methods to form your automation script. Installation. To get your self started with the robot framework you need to have the following list of technologies with you. Python (2.7) -  http://python.org WxPyton -  http://wxpython.org Chrome driver at your project location If want to connect to your Database then you need to have Visual C++ Redistrib
Read more

Test Automation With Cucumber

Test Automation What Is Cucumber As per my understanding cucumber is a framework that is built tagetting the user acceptance testing scenarios. In other words it is forcused on making the human readable test cases as example scnarios. So anyone who is checking or creating the script can understand the scope, failed and passed scenarios and where did the fail scnarios were. Other than than cucumber + selenium will provide you few awesome reports ( this might make you automate everyting :D ) The Basic Ingredients IDEA or Eclipse Java - gradle Selenium Cucumber JUnit or TestNG How It Works
Read more