Basamma Patil

• Designed 53 test cases for Mshop: iOS and Android, Mweb: iOS and Android platforms as per business requirements.
• Increased effectiveness of virtual book bundles through the creation of targeted test cases for both T1 and T2 treatments, covering both Prime and Non-Prime accounts.
• Reviewed and incorporated suggestions from all stakeholders in the Test Plan execution process.
• Took responsibility for the entire project lifecycle, encompassing Writing Test Cases, Test Case Reviews, Test Execution, Bug Reporting, and Tracking.
• Took key responsibilities in performing :
  1)Functional testing: This is Front end UI testing, tested both on Test and Gamma environment.
  2)Regression Testing: In this testing DP, Cart and Checkout flow is verified.
  3)I have performed DP mandatory testing which includes following tests under it Compare
  Tests,URL Checks,Fatal Checks.
  4)At the end of 1 st iteration, identified 10 bugs which included blocker and non-blocker issues.
• Provided post-bug fix support and performed necessary regression tests for existing features.
• Included in QA Sign Off process by capturing critical information like 'Customer Experience', bug resolutions, potential risks.
• Presented a detailed Test Execution Summary report on the Go-No-Go wiki for all stakeholders.
• Provided the KT for other QA peers to have knowledge on the project for future reference.

• The test plan was created by a senior QAE, and I was responsible for executing some of the test cases in this project.
• YO orders page for checking the messages that were displaying after each re-consultation.
• I went about testing all the rejection use cases possible in the Nautilus and how the experience pans out for customers over YO and the notifications.
• I also led the integration testing with Letsdoc in the production environment and helped the team gain confidence in the post-order customer experience and the integration between the TMP systems and the Amazon systems.
• I tried to show ownership in reaching out to the engineering team for any issues identified and proactively suggesting any improvements in the proposed experience.
• This included database testing and tested for respective table updation
• I was able to make significant contribution to the UAT while managing my key responsibilities alongside.

• Writing Test Cases, Test Case Reviews, Test Execution, Bug Reporting and Tracking
• Excellent in Preparing, Peer-review and Execution of Test Cases
• Well versed in Defect tracking, analysis and reporting
• Experience in creating trouble tickets for reporting issues to the developers
• Proficient in Test Case Reviews, Test Execution, Bug Reporting and Tracking
• Experience in IAP testing and handling the issues related to them
• Experience in Publishing the Apps to Live
• Experience in handling negative customer reviews
• Trained new joiners in various projects and made them productive within short period
• Expertise in Bug Tracking Process, Familiar with Bug Reporting and Tracking Using Bug tacking Tools like Jira and Paragon (Internal Tool).

• The test plan was designed by the senior QAE, and I executed most of the test cases.
• Test Plan included nearly 1,000 test cases. The scope of testing will be limited to Subscribe and Save Program on Desktop, Mobile Web and Mobile Application (both iOS and Android) for IN Marketplace. I have worked on all the platforms.
• Mainly, I have worked on the following scenarios:
  1. End to End Feature Testing
  - Subscription Creation for Autopay Onboarded Customers via Legacy, Retail Checkout flows
  - Manage your Deliveries
  - E-mandate Setup before and during the restricted period
  - Auto Charge for P0 and Recurring Orders
  - E-mandate Modification and Cancellation
  - E-mandate Setup and Cancellation In-Progress
  - Event Processing to and from RPP Platform
  - Customer Notifications
  
  2. UI Component Testing
  
  3. Customer UX Regression.
  - Subscription Creation using Legacy and Retail Checkout.
  - Pay Now functionality on MYD.
  - Pages on Legacy Flow: PSP, ASP, and SPC.
  - Pages on ONML Flow.
  - Subscribe via Cart and Checkout.
  - Subscription via Carousels on MYD.
• As I was part of the exploratory testing, most of the above scenarios were covered during exploratory testing.
• In total, I have executed 200 test cases as part of functional testing, which includes Inactive, Inactive: Trying to Setup, Setup Initiated, Cancel Initiated: Throttling to Active, Inactive Cancel initiated, and Inactive: Cancelled Status.
• I have discussed issues with the developer as a part of re-testing the bug fixes.
• Post bug fixes, bug retesting has been performed, and regression is done on existing functionalities.

.

• Test Plan was not required as it is OE in take which is just bug fix and not main project
• This is mainly database testing in which I need to specifically check whether the rows are updating correctly or not according to the snapshots processed
• Worked on AWS: Dynamo DB: This included database testing and tested for various tables
• As it is bug fix, no issues are observed as such when executing the scenarios and some observations are discussed with respective developer to get clarifications on the concepts.

• Test Plan was designed by BuyX team and I owned the Test execution for consumables WDGs in IN marketplace
• 4 different platforms were defined for testing MWeb (Android and iOS), Mapp (Android and iOS)
• In total, 58 test cases were derived which need to be tested on 4 platforms with 3weblabs based on dimension of an ASIN (1D, 2D and 3D)
• Able to complete the testing with committed timelines
• As part iteration 2 of the project, again team has requested for assistance in testing for 2 consumables WDGs in both US and IN marketplaces
• Same been taken care by me and detailed report has been sent post execution.

• Along with Functional Components Testing I have performed Exploratory testing also
• Ramped up quickly on the re-consultation workflows
• As Concept was little complex in this project spent little extra time to read the test cases and grasp the concepts here
• Had the opportunity work on AWS: Dynamo DB
• This included database testing and tested for respective table updation
• No issues are observed as such when executing the scenarios and some observations are discussed with respective QAE to get clarifications on the concepts.