KRANTHI KUMAR K

• Analyzed Business Requirement Specifications to clarify project objectives and testing scope.
• Participated in manual and automated testing during software development lifecycle.
• Established and maintained automation environments using Eclipse, Java, Selenium WebDriver, and BDD Cucumber with TestNG.
• Developed automation scripts with Selenium WebDriver and Java, employing various locators and custom XPaths.
• Executed test scripts, analyzed results, and logged defects using JIRA.
• Raised and tracked defects while collaborating with developers on verification of fixes.
• Integrated exception handling in scripts to enhance test execution reliability.
• Conducted regression testing for each new build, including functional, smoke, and re-testing cycles.

• Evaluated Business Requirement Specification to inform testing strategy.
  Engaged in manual and automated testing to ensure thorough application validation.
  Configured Automation Environment with Visual Studio, C#, Selenium Web Driver, and Spec Flow Framework.
  Produced test scripts using Selenium Web Driver integrated with C# programming language.
  Executed tests, reviewed outcomes, and maintained updated status reports.
  Identified and documented defects while verifying fixes through retesting efforts.
  Contributed to planning sessions and daily scrum meetings for automation updates.
  Conducted regression testing alongside functional and smoke testing methodologies.

Reviewed Business Requirement Specifications to define manual testing scope and objectives.

• Participated in study configurations and test planning for effective manual validation.
• Prepared test environments, ensuring readiness for comprehensive manual test execution.
• Selected and prioritized test cases based on business impact and feasibility criteria.
• Utilized inspection tools to locate UI elements and applied identification strategies.
• Designed detailed test scenarios and steps for precise validation of UI components.
• Executed manual test cases across various modules and documented results thoroughly.
• Logged defects with clear reproduction steps, collaborated with developers for resolution, and updated test statuses accordingly.