
Seeking a challenging role in Automation Testing and Quality Management.QA Test Engineer with 3+ years of comprehensive experience across the entire Software Testing Lifecycles(STLC).Specializing in both manual and automated testing for web and API applications. Expert in transforming manual test cases into scalable automation frameworks using Java and Playwright. Proficient in analyzing business requirements, designing detailed test plans, and performing thorough functional, regression and exploratory manual testing.
In our day-to-day ST (Sanity Testing) cycle, updating the Jira Kanban board has largely been a manual and repetitive experience. Each cycle requires us to monitor Microsoft Teams channels for environment UP notifications, navigate to the ST Tool board, drag cards to IN PROGRESS, wait for pass/fail/blocked results, and again manually move cards to DONE or BLOCKED, often with CDEX defect IDs that need to be linked separately.
For teams handling multiple releases and environments such as R2604 INT B, R2606 MPIE, and UPIE .we often find ourselves switching between Teams and smoke test Tool of times a day, copy-pasting defect IDs, and repeatedly posting consolidated ST status updates to Daily Huddle.
ST Tool Bot automation is a local utility that monitors Teams channels in real time and drives the official Jira ST Tool board through a real browser using Selenium + Jira REST APIs with saved session state, so routine ST board updates become automated, config-driven and repeatable.
Teams → iTrack sync tool so investigation work in chatrooms is automatically preserved in CDEX defects, saving manual work and keeping defects properly documented.
It helps to Keep the CDEX defect in iTrack updated as the single source of truth for what was investigated, who said what, and when without engineers manually copying Teams chats.