SUMMARY

• Experienced Full Stack Software Development Engineer in Test (SDET) with over 5+ years of experience in the Insurance, Banking, and Financial services industry
• Perform Automation Testing focusing on all layers of applications including UI, API, and DB
• Identify and use unique Web Element Locators with Selenium WebDriver making web UI Automation Test faster, more accurate, and easier maintainable
• Implement Software Testing Life Cycle (STLC) and Software Development Life Cycle (SDLC) process to Test Software in Agile Development Framework
• Perform API, and Database Testing using REST*Assured Java Library and JDBC Driver to validate XML & JSON schema ensuring correct API’s functionality, reliability, performance, and security
• Conduct Back - End Database Testing using Data-Driven Testing (DDT) approach for RESTful APIs utilizing JUnit 5 Parameterized Tests helping developers to save time by making Tests dynamic and faster
• Use Java, Maven, Cucumber, Jenkins, Jira, and Selenium WebDriver as tools in Behavioral Driven Development (BDD) Framework to Automate Test Scenarios written in Gherkin language which effectively saves time, cuts operating costs and improves the company’s operating efficiencies
• Manage Database through RESTful APIs using HTTP Methods such as Post, Get, Put and Delete operations to ensure Database is UpToDate

TECHNICAL SKILLS

Programming Languages: Java, Gherkin

Standards & Protocols: XML, HTML

Database(s): Oracle, MySQL, PostgreSQL

Operating Systems: Windows 11

Environment: Apache Maven, Agile, Jenkins, SQL, Selenium WebDriver, Cucumber, Karate, JUnit, TestNG, Hamcrest, Git, GitHub, IntelliJ IDEA, Jira, Postman API Platform, Swagger, DevOps, BDD, REST, JDBC, CI/CD

Computer Basics: MS Word, Excel, Access, and PowerPoint applications

Cloud: Amazon Web Services (AWS), Amazon Elastic Compute Cloud (EC2)

PROFESSIONAL EXPERIENCE

Software Development Engineer in Test (SDET)

Confidential, New York, NY

Responsibilities:

• Conducted static Testing of Software Requirement Document (SRS) to assess the accuracy and completeness of all requirements to prevent issues in the early state of software development
• Use Postman, and Swagger to understand the response and structure of APIs consequently building successful automated API Testing
• Implement customized and JUnit Test annotations such as @Test, @Before, and @After tags to run Selenium WebDriver Test Codes in Behavioral Driven Development (BDD) Framework allowing to run specific Test Case Scenarios from Cucumber features file
• Manually Tested functionality of each Test Scenarios and criteria in UI to ensure correct functionality of each module and feature before automating it
• Inspected and located each web element in Document Object Model (DOM) using CSS, Selenium XPath, and other selectors to navigate through HTML, and XML pages to Automate Test Cases
• Performed Positive and Negative Test Case Scenarios to confirm correct functionality of Software application
• Use TestNG and JUnit for Testing Test Scenarios and Test Cases
• Conduct Regression Unit Testing using JUnit Test methods with Selenium WebDriver to Automate Tests and assert expected match with the actual result, allowing to write structured, short, and better Test Cases
• Effectively use Selenium WebDriver for automating Web-based cross-browser Tests simultaneously Testing several applications at the same time enabling to work faster and identify potential bugs quicker
• Manage and update dependencies in Maven to keep all versions UpToDate to develop and build successful Tests
• Run Maven mvn clean Test for all classes to remove all stale files from Java source code so that old results from the last compile are not included in the next compile making Java code clean and fresh
• Validate JSON Schema in APIs response using REST-Assured Library and Maven JSON Schema Validator dependency in POM.xml file
• Use Java Database Connectivity (JDBC) or Java API to connect with Oracle Database to run Structured Query Language (SQL) Query and use it in Java code path to Automate Tests enabling quick communication and Testing of Database
• Utilize Java’s Object-Oriented Programming (OOP) concept using abstraction, encapsulation, inheritance, and polymorphism creating methods and variables in different classes and re-use in different classes making the entire framework flexible, reusable, and effective
• Use Page Object Model (POM) framework to store all web elements in Page Object class that holds all functionality and features of the web page which removes code redundancy, allows flexibility and reusability to Automate Tests
• Implement Behavioral Driven Development (BDD) Framework using Gherkin language in Cucumber feature classes wrote Test Scenarios (TS), Test Cases (TC) which enabled complete Test in plain English making easy for other users such as stakeholders without programming experience to understand the Testing process Framework
• Use Java programing language to Automated the Test Scenarios leading company to save time and use efficiently
• Maintain Smoke Test Suite with 20 Test Cases
• Use Continuous Integration and Continuous Deployment (CI/CD) Pipeline in Jenkins and Amazon Web Services (AWS) Cloud server to run externally Regression, Smoke, and other Tests to generate Cucumber Test reports to discover Software flaws
• Attend Backlog Grooming, Stand-Up, Sprint Planning, and Sprint Demo meetings to effectively improve and adjust current and future sprint planning
• Maintain all necessary dependencies in POM.xml making the Framework UpToDate

Quality Assurance (QA) Engineer

Confidential, New York, NY

Responsibilities:

• Performed Manual Test of User Interface (UI) to ensure all features and modules are functioning correctly
• Use Postman to manually Test Application Programming Interface (API) to check the response of APIs query parameters
• Implemented Karate Automation Framework for some Smoke Tests which allows avoiding step definition and runner classes making Test Structure easy to understand for non-programmers
• Checked HTML report for details of failed steps, documented with screenshots and presented to developer team making it easier to understand for developers which part of the Test was relevant to the failure
• Maintained Karate-config.js JavaScript (JS) file with all necessary configurations variables like URLs and environments keeping continuous Test configuration correct
• Generated Authentication and Authorization token in Postman that enabled authenticate of future requests for Representational State Transfer (RESTful) Web Services API Testing
• Executed Database/Back-End Testing by writing SQL Queries along with JDBC for Data validation and integrity
• Manually verified response status code, payload body format, and headers in Postman to confirm correct functionality of API