profile-pic
Vetted Talent

Vivek Kumar

Vetted Talent
To leverage my 11.6 years of experience in Automation Testing and QA leadership with a strong emphasis on Cucumber BDD, Protractor, WebdriverIO, and continuous integration tools such as Jenkins, contributing to project support and test process compliance
  • Role

    Senior Principal Engineer - Quality & Assurance Testing

  • Years of Experience

    12 years

  • Professional Portfolio

    View here

Skillsets

  • Automation Testing - 12 Years
  • Automation Testing - 12 Years
  • QA Automation - 12 Years
  • JavaScript - 4 Years
  • Java - 8 Years
  • Type Script - 4 Years
  • Type Script - 4 Years
  • Git - 8 Years
  • Cucumber - 8 Years
  • Maven - 8 Years
  • Jenkins
  • BDD
  • API Testing
  • Protractor
  • WebdriverIO
  • QA Lead

Vetted For

4Skills
  • Roles & Skills
  • Results
  • Details
  • icon-skill_image
    Senior Test Automation EngineerAI Screening
  • 69%
    icon-arrow-down
  • Skills assessed :Manual Testing, Selenium, Automation Testing, Jenkins
  • Score: 62/90

Professional Summary

12Years
  • Mar, 2021 - Present4 yr 11 months

    Senior Automation Tester

    Mercer Consultancy India Pvt Ltd
  • Mar, 2021 - Present4 yr 11 months

    Senior Principal Engineer - Quality & Assurance Testing

    Mercer Consultancy
  • Oct, 2015 - Mar, 20215 yr 5 months

    Test Analyst

    Infosys
  • Jun, 2012 - Oct, 20153 yr 4 months

    Senior Consultant

    Capgemini India Pvt. Ltd.
  • Oct, 2015 - Mar, 20215 yr 5 months

    Test Analyst

    Infosys India Pvt. Ltd.

Applications & Tools Known

  • icon-tool

    Visual Studio Code

  • icon-tool

    Eclipse

  • icon-tool

    Git

  • icon-tool

    Jenkins

  • icon-tool

    Jira

  • icon-tool

    HP ALM

  • icon-tool

    Maven

Work History

12Years

Senior Automation Tester

Mercer Consultancy India Pvt Ltd
Mar, 2021 - Present4 yr 11 months
    1. Responsible for End to End Automation Framework in WebdriverIO with Typescript/JavaScript.
    2. Drive Test Automation And helping to drive continuous improvement in automation practices
    3. Prepare high-level and Detailed test estimates for manual, automation & API testing.

Senior Principal Engineer - Quality & Assurance Testing

Mercer Consultancy
Mar, 2021 - Present4 yr 11 months
    Responsible for End to End Automation Framework in WebdriverIO with Typescript/JavaScript. Drive Test Automation and continuous improvement in automation practices. Prepare high-level and detailed test estimates.

Test Analyst

Infosys
Oct, 2015 - Mar, 20215 yr 5 months

           

    Involved in Test

    planning & estimation, and onshore-offshore communication.

           

    Experience in using HP

    ALM for Test Management, execution and reporting.

           

    Creating

    selenium/Protractor scripts for automation using cucumber BDD and maven

    integrated framework.

           

    Anchoring

    Retrospective, Innovation & Ideas meetings & events.

Test Analyst

Infosys India Pvt. Ltd.
Oct, 2015 - Mar, 20215 yr 5 months
    Involved in Test planning & estimation, onshore-offshore communication. Using HP ALM for Test Management. Creating selenium/Protractor scripts with cucumber BDD framework.

Senior Consultant

Capgemini India Pvt. Ltd.
Jun, 2012 - Oct, 20153 yr 4 months
    Defect logging, reporting and tracking to closure. Functional, GUI, Security, Regression Testing. Execution of test cases based on User stories or FRS documents.

Achievements

  • START OF THE MONTH Mercer July-21
  • INNOVATOR award Infosys Sept-19
  • PIONEER award Infosys March-18
  • Yaro Ka Yar (Team Player) award Capgemini June-2014

Testimonial

Mercer

GBMA

Vivek Kumar

Major Projects

3Projects

Global Health Benefits

Mercer
Mar, 2021 - Present4 yr 11 months

    Global benefits management offers multinational organizations an effective way to manage insured employee benefits around the world. Global or regional arrangements offer visibility, control, cost savings and ensure consistency in governance, while delivering solutions that are based on local country needs.

Global Benefits Management (GBMA)

Mar, 2021 - Present4 yr 11 months
    End to End Automation Framework in WebdriverIO with Typescript/JavaScript for Mercer, US.

BT Financial Group Australia (BTFG)

Westpac Banking Corporation, Australia
Oct, 2015 - Mar, 20215 yr 5 months

    Westpac Banking Corporation, Australia

Education

  • Masters of Coumputer Science & Engineering

    Guru Nanak Dev University Amritsar (2011)
  • M.TECH in Computer Science & Eng.

    Guru Nanak Dev University (2011)

Certifications

  • Java

Interests

  • Watching Movies
  • Listening Music
  • AI-interview Questions & Answers

    Hi. This is, uh, Vivek Kumar. I have total of 12 years of experience into automation function and manual, uh, testing. Out of 12 years, I have 9 years of, uh, experience in early into automation testing using various tools like Selenium with Java, WebDriver with TypeScript, Cypress. And, uh, currently, I'm working with, uh, Mercer India Private Limited. Here, uh, my current role is to, um, automate a web UI, which is developed in Angular JS. And, uh, there for the same reason, we are using the, uh, Node JS based framework, which is WebDriver IO using TypeScript. For the CICD purpose, we are using Jenkins, and for code management purpose, we are using, uh, Git and GitHub. And for test management purpose, we are using Jira. Also sorry. Also, for, uh, nonfunctional testing, uh, like, for performance testing, we are using JMeter. We are creating our scripts in JMeter and running those scripting Blazemeter, uh, like, on cloud.

    Okay. So synchronization issues can be fixed with the with the help of, uh, the functionality provided by Selenium, uh, which is, uh, explicit weights. So we have 2 type of explicit weights. Uh, 1 is web driver weight, and the other one is fluent weight. So using, uh, those waits, we can handle the, you know, synchronization issues in, uh, web driver scripts. So, uh, for implicit wait, uh, we are, like, uh, putting expected condition on a particular element. And for a fluent wait, we are, uh, we are setting up a time, uh, you know, to check for the element, uh, visibility or presence of element in regular interval of time. So you can say we are using the polling in fluent weights.

    Okay. So, uh, test data, uh, to a Selenium script can be provided, uh, like, you know, uh, through various ways. So if you're using the data driven framework, then your data, uh, should come from any other external files. That would be any, uh, text file, uh, Excel file, or maybe, uh, DB connection you can create. And, uh, for further, like, if you are using a Cucumber b a d based framework, then you can, uh, use, uh, test data directly into your feature files, uh, by putting, uh, examples or scenario outlines. Uh, you can pass the test data.

    Okay. So, uh, for that, we need to implement page object, uh, model design pattern so that, uh, we need to have a minimal changes on, uh, on the locator part of our applications. So that that will be that will make your, uh, framework as, uh, stable. And, uh, also, you need to, um, uh, implement some utilities. Uh, if there's some common utilities with respect to your application is there, you can implement, uh, those so that, uh, as your application, uh, grows, uh, you can, uh, you know, handle those, uh, changes, uh, you know, uh, efficiently.

    Okay. So if you have APIs, uh, in, uh, like, in your project to be tested, we can implement a rest assured framework with the Java, uh, to, uh, you know, uh, automate your, uh, API testing. So, uh, so, like, selenium in specifically selenium, there's no nothing, uh, related to API testing. Selenium is only for, uh, web, uh, automation, but we can use, uh, rest assured, uh, framework to, uh, test our RESTful APIs.

    How to integrate how to integrate performance testing within your Selenium test suite? Okay. So, like, Selenium is made of 4, uh, components, um, offering different performance testing and automation features for web browsers, like, uh, Selenium remote control, we can, uh, use, and maybe Selenium grid, uh, we can use. Uh, also, like, uh, for performance testing, we have a JMeter and Selenium that can be used together for load testing of a website. Uh, so Selenium is used to, like, perform load testing, and JMeter is used to measure performance, uh, testing. Uh, once you measure, like, how fast HTML pages take to load and also check JavaScript and CSS performance. So, uh, like, we can use, uh, the graphical Jmeter interface and some scripting to invoke Selenium code, uh, to, you know, uh, do the, uh, testing.

    Review this API scores. They cannot could result in pro to check this to do a status code. Response code is dot get. Response dot status code. What would you suggest to improve the check for the HTTP status code? Okay. So it should, like, you know, it should always return 200. So we can add another assertion or condition so that it doesn't return any other code than like, 200 ones. So we can, like, uh, put the kind of health check status. Like, that is 200 only. I believe it should not return any other code than, like, uh, 2xx. So I think that we can check.

    Mistake is made here considering such a human and given the user on the login page when the user enters a relationship, then the user should be redirected to the dashboard and should see that too much. But when the user click log out, then the user should be redirected to login page. Okay. So I think, uh, in place of but we can, uh, use when again. The rest I I feel it is, uh, good.

    Describe an optimal approach for creating a scalable and untenable test framework using Selenium and Jenkins. And describe optimal approach for getting a scale and a minimal test framework using Selenium and Jenkins. Okay. So, uh, so, uh, suppose we have created a 2 cumber b r d framework, uh, in, uh, selenium, and, uh, we we want that, uh, those tests to be run, uh, as soon as there's a deployment on our, uh, on our test, uh, environment. So to to automate that process, what we can do, uh, so suppose there is a one job which is deploying some code to your test environment, so, uh, we'll make that job as a upstream job, and, uh, uh, then we'll create a Jenkins job, which is a test job. We'll, uh, mark that job as a downstream job. So we will, uh, create, uh, like, Jenkins script, which will, uh, identify once the deployment of upstream job is successful, then trigger our test job automatically. So, uh, so in that job, we can add add, um, like, we can create that job like, we can configure that job in such a way so that, uh, you know, uh, in post build actions, we get a report, uh, on our emails, and we get to know what is the, uh, result of our, uh, test, uh, so which has executed. So we can we also can like, yes. We need to configure it with the git, uh, GitHub in, uh, git section of Jenkins. Then in, uh, build section, we need to pass, uh, like, which file we want to embed. So suppose if it is a framework using Maven or test NG, so we can invoke the dot XML file, uh, using Maven options in, uh, uh, build actions. And post build action, we can configure how the reporting should be. Uh, so and once that test is done, so who, uh, who are the people should receive the report or the status of execution?

    How could you employ manual testing skill to complement your automation strategy when using? How could you employ manual testing skills to complete? Okay. So, uh, so I believe, like, uh, manual flow of your application or manual, uh, you know, manual testing, you need to have knowledge of that unless you won't be able to, uh, you know, effectively complete your automation process. So, um, whenever you are creating any automation framework, so you need to understand the manual flow of your application so that in in your automation, uh, code as well, you can put that flexibility, uh, like, uh, and, also, you can optimize your code with respect to, uh, the, you know, application flow. So suppose there's a there's a end, uh, test case which you are validating, and for that, you already have, uh, created a test data. Okay? But that test data in some other script. But you know that that particular test data is, uh, like, you know, applicable to the other test which you are testing. So, uh, you need to separate the, uh, you can say, the test data from your, uh, you know, test cases so that that common test data can be used at multiple, uh, script. So that kind of knowledge, you'll only get from manual, manual testing skill.

    Do take to use Jenkins as part of BDD strategy with Selenium? What approach would you take to use Jenkins as a part of PDD strategy? Jenkins' CIC tool and BDD views in Cucumber. And we we can have that, uh, like, you know, connection. Like, BDD can be connected to Jenkins using framework only. So I'm I'm not sure about, uh, on this.