I worked on the web application testing for the incremental development of a new insurance product-selling website for a client. The development and all workflows were managed on Azure DevOps. I participated in User Acceptance Testing (UAT) on DevOps, where user stories were created and provided with scope and business context. As soon as the application related feature was deployed from the SIT environment to the QA environment and then to the UAT environment, we initiated our testing phase. This involved creating Requirements Traceability Matrices (RTM) or Test Case Documents (TCD) based on the given requirements & executing the scenarios & then the bug was raised accordingly.
Proven Automation Engineer with a track record at Qualitykiosk Technology for Kotak Life Insurance, excelling in functional and automation testing. Mastered Agile methodology, enhancing test efficiency and accuracy. Demonstrated leadership in debugging and regression testing, significantly improving software reliability. Skilled in fostering team collaboration and driving project success with keen attention to detail and innovative problem-solving.
Client: Kotak Life Insurance
Project name: Optimus: A Web Application
From 2023 May & Current
From January 2023 to April 2023
The client provided a Business Requirements Document (BRD) outlining the need to integrate a new combi product into their web application, Genie. A senior colleague supplied the Test Case Document (TCD), and I carried out all the scenarios specified in it. Each scenario was required to meet the expected criteria; if any did not, the test case would fail, prompting me to log a corresponding bug report.
From July 2022 to December 2022
This was my first project in Kotak Life Insurance on an insurance-based savings product.
The client provided a Business Requirements Document (BRD) for onboarding a new product called Kotak Guaranteed Fortune Builder to their web application, Genie. A senior colleague provided the Test Case Document (TCD), which outlined the scenarios that needed to be executed. I was responsible for running all the scenarios to ensure they met the expected descriptions. If any scenario did not meet the requirements, the test case would fail, and I would raise a corresponding bug report.