We provide IT Staff Augmentation Services!

Java Sdet Resume

3.00/5 (Submit Your Rating)

Tysons, VA

OBJECTIVE:

  • I have been working as a Java SDET Engineer and am looking for a new opportunity to create and grow. I am experienced with Java OOP, Selenium Automation, API Automation, and SQL and Database languages.

SUMMARY

  • Using Cybertek School for Automation and SDET Engineering, I have been a part of a year - long program to learn about various programming and Software Testing tools such as: Java, Java OOP concepts, JDBC, Maven, Selenium WebDriver, JUnit, TestNG, Cucumber, Gherkin, Postman, REST Assured Library, API Testing, API Web Services Testing, and others.
  • I took place working for various internships (non-paid) scheduled by the school in order to hone my skills in the real world and in real situations.
  • My coding foundation is in Java, and I am familiar with Java Object Oriented Programming (OOP) concepts such as: Encapsulation, Inheritance, Abstraction, and Polymorphism.
  • I am proficient in HTML and CSS language structure, using it for online-based Software Automation Testing with programs such as: TestNG, Selenium, and Cucumber/Gherkin.
  • I mainly use the Agile Scrum Methodology of Software Development Life Cycle, though I do have knowledge about Kanban, XP and other Agile Methodologies, as well as the Waterfall Methodology.
  • I have been a part of numerous Grooming, Sprint Planning, Daily Stand-Up, Demonstrative, and Retrospective Meetings, and understand how Test Cases are prioritized, given points, and assigned to team members by the Product Owner (PO).
  • My BDD Framework uses Cucumber mainly. The main coding language for it is Java and it uses a Maven build Automation tool with a POM.xml for controlling dependencies. Cucumber uses utility class files such as: Pages, Runners, Step Definitions, Hooks, and Features.
  • I have used REST Assured API and API Testing to ensure that programs and software are able to communicate with each other accurately.

TECHNICAL SKILLS

Testing Tools: Jira, Selenium, Cucumber, Gherkin, REST API, TestNG, Postman, IntelliJ IDE

Languages: Java, HTML, SQL, C++

Test Management Tools: Jenkins, Maven

Databases: JDBC, SQL

PROFESSIONAL EXPERIENCE

Confidential, Tysons, VA

Java SDET

Responsibilities:

  • Confidential is a Web-based Fleet Management System mainly dealing with the cataloging, maintenance, and documenting of delivery trucks.
  • My team was responsible for the Fleet Module System which handles Contract Management and Vehicle Information.
  • As opposed to the previous internship, Confidential Testing implemented BDD Testing Frameworks through the use of TestNG, Selenium, and Cucumber.
  • API Testing was also used to ensure that requests could be put in from the Confidential site to the Database, with specific Queries SQL Queries being pushed to test said Database.
  • Using these softwares both Front-End and Back-End Testing are performed.
  • Part of implementing Front-End Testing (TestNG, Selenium, Cucumber) are the various utility files and the POM.xml file to control and manage dependencies.
  • Specifically, the WebDriver class and method were important for setting up Automated Testing, and the Page Object Model helped us create separate classes for each page of the Website, allowing for a streamlined Testing experience, resulting in cleaner and easier to read code.

Environment: TestNG, Selenium, Cucumber, Gherkin, Maven, SQL Database, JDBC, REST Assured API

Confidential, Tysons, VA

Java SDET

Responsibilities:

  • It allows staff, students, and administrators to schedule conferences across different locations.
  • It also enables management to add, update, or delete users, as well as manage the campus, clusters, and rooms.
  • There I applied my knowledge of the Software Development Life Cycle (SDLC) and the Waterfall and Agile Scrum Methodologies, including the 5 meetings: Grooming, Sprint Planning, Daily Stand-Up, Demonstrative (Demo), and Retrospective (Retro).
  • At the beginning of a new sprint, my team and I would groom Test Cases using the Fibonacci sequence and assign points to each of them.
  • From there we would assign these Test Cases by points to various members of the team depending on the load, each member would get about 5 point Test Cases individually and anything larger than these would be broken into multiple sections.
  • I used Jira and GitHub for creating and linking Test Case Scenarios, bug tickets, etc. and used various Git methods (such as push, pull, branch) to upload files to online company repositories.
  • Towards the end of the project I used Jenkins for Regression Testing, Integration Testing, and Smoke Testing.
  • Whenever Automation Testing could not be performed, or was not appropriate to the situation, I performed Manual Testing. Regression Tests were done at the end of every sprint.

Environment: Java, Jira, Jenkins, GitHub, Git, HTML, Dev Environment, Staging Environment, Testing Environment, Production Environment

We'd love your feedback!