Kiran Talla

• 5 years 5 months of Quality Assurance Engineer experience encompassing wide range of skill sets over Automation Testing via Selenium WebDriver with Java as language binding, Diamond Toolkit, Carbon, Git, API Integration Testing on Native AWS - Hydra Platform
• Extremely good at writing code in Java using its Object Oriented Principles
• Proficient in performing Testing activities associated with Automation and are related to Amazon Customer Service Technology, Workforce Management, Amazon Logistics and Amazon Exports and Expansions using Java technology
• Proficient in configuring the jobs and QA Approval workflows to run the Continuous Deployments
• Good understanding over the QA core competencies like Test Planning, Test Strategy, Test Case Enumeration.

Project Sunrise - Amazon EG launch

Project Sunrise targets launching 3 Amazon marketplaces in the middle east region (UAE, KSA and Egypt) and migrating Souq’s business to Amazon. As part of the Sunrise project - EG launch, I divide it into 14 primary consumer work-streams. The QA team needs to develop a test strategy for testing different categories, from Amazon Secure Sign-in, to order placement, delivery tracking, and returns.

• I’ve led the QA team by developing a test plan and having it reviewed by the stakeholders across the network, including the Product Managers, Program Managers, TPMs, and SDMs.
• I’ve designed the test timelines in a working backward manner in accordance with the launch dates, along with a defined set of goals. As the test execution has to be performed across all the 14 different streams, it was difficult to keep track of each detail.
• To track the execution details and test coverage, I've created separate test runs in the testrail to track the execution status of each workstream separately.
• Partnering with the Device Associates, part of the AEE operations team in Chennai,
• I’ve conducted multiple phases of testing milestones like integration, end-to-end, regression, and sanity. I leveraged the existing tester resources every day, focusing on the critical components of the website.
• I have created multiple trackers to track every single detail, including test execution status, test coverage, and UAT and F&F Readiness. The trackers were updated at every bug triage meeting, having them reviewed by SDMs and product teams.
• To segregate the reported bugs, I’ve created labels for each workstream and added the relevant label to every bug report, which helped us filter the bugs based on the workstream.
• There were ~80 test cases that were blocked by ASIN Test data and 81 test cases that were blocked for execution for various reasons. To unblock them all, I’ve collated the details in the quip sheet. Based on that, along with the Device Associates, I’ve dived deep and figured out the root cause. Then we followed up with the concerned teams and had them unblocked.
• Scheduled recurring meetings with the stake holders for bug triage, discussing the blockers and getting the test data for execution. I collaborated with the RBS team manager, product managers, and QAM to unblock the test execution from ASIN data.
• Published the weekly report, which covered the important details of the project, including the execution status, bugs reported, assigned bug followup, and execution completeness details across each workstream, along with the link to access the testrail and bugs for each workstream individually.
• To increase the coverage, I realized a fresh pair of eyes could explore the features from a different point of view. Hence, with the approval of the AEE management team, I’ve conducted the "Bug Bash-CE EG Play Day" across the entire AEE org to uncover more bugs other than the test cases. With this, we were able to uncover 52 bugs and rewarded the top two bug reporters for their effort.

• Project: Amazon Poland Website Launch
• We launched Amazon Poland Website as a full store, allowing customers to purchase over 141 million physical products in Poland, the largest product offering of any store in country
• Amazon offers customers affordable prices on a wide range of products from popular categories like books, toys, electronics, fragrances, cosmetics, housewares, and fashion, thanks to their global product access.
• Responsibilities: - Created a test execution strategy for executing ~9000 test cases co-ordinated with the Device Associates part of AEE Operations team location in Chennai. - Conducted multiple phases of testing milestones like Integration, end-to-end, regression and sanity. - Leveraged the existing tester resources everyday focusing the critical components of the website - Published weekly reports with the test execution progress and the defects identified - Triaged the bug reports and worked with the development teams by defining the severity and followed up till the closure. - Worked with the Product Managers and Software Development Manager to identify the Launch Blockers and marked those issues as high priority for fixes. - Worked with multiple host teams to generate the test data required for execution of test cases
• (example: Test ASINs, Deals, Offers, Promotions, Orders, Shipments etc).
• Automation: - Automated the P0 cases to run in the regression workflows. - Customized the existing test framework to accommodate and onboard test execution for new marketplaces.

• Project: CSAmazonLogisticsGoa Pages UI Automation
• Team owns complete tech infrastructure for customer support tools related to Amazon logistics(AMZL) and Ship With Amazon(SWA) use cases - Driver and Recipient contact landing page, Off-road support portal, Shipper portal, Easy maps - A map based solution to handle Unable to Locate(UTL) use cases, Pre-emptive customer support through customer service, In-transit actions workflows(Stop and Return, Add delivery instructions, Reschedule delivery)
• I was tasked with designing, developing and delivering test strategy for CS Amazon Logistics Goa Front End applications which powers up multiple pages and workflows in Customer Service Central (CSC) for Amazon Logistics use cases.
• Responsibilities: - Created a detailed Test plan which comprises all the features and UI components of Recipient and Driver Landing Pages along with Order Detail Page workflows working with stakeholders and developers in the team - Created a generic and standardised test plan for future marketplace launches plugged in with all the inputs from SDMs, Product team, and developers that can be used as a template for all the new Marketplaces Launches. - Automated Test Coverage for Each component/feature; improved automation percentage from 30% to 80% - Seamless execution of automated tests with informative test reports for tracking and troubleshooting. - Project: Amazon Logistics - Marketplace Expansion - While CSAmazonLogistics Team progressively developed the RCLP and DCLP pages at a very fast pace, quality testing during the launches was still a challenge
• It consumed approximately 7 to 10 days of Developer time in setting up the test suites and performing the testing with multiple delays and blockers
• I've come up with Launch Testing strategy which included the following: - Created a standard process template to achieve consistency in terms of testing across all the new marketplace launches. - Organise the Test Scenarios according to the testing type - Create Common Test Suite for Launches and add the detailed test cases which are in common for all the marketplaces. - Automate the test cases which meets the automation criteria - List of marketplaces launched using UI Automation based with Launch Readiness Test Strategy are CA, ES, FR, IT, SG, AU, MX, JP. - Project: Service Integration Test Setup on Native AWS Services - Backend Services powering up all the Amazon Logistics Application were migrated to Native AWS stacks
• Testing the integration of services along with the environment validation was challenging
• Below are the responsibilities that were taken up and delivered: - Onboarding to Hydra Test Platform - Create AAA applications for Integration Test Packages - Attach policies and IAM roles to the AAA applications - Connecting the test resources to resource server - Onboarding Coral Clients with CloudAuthSetting up and documenting local test environment to enable writing tests and execute them over RDE. - Executing the tests on AWS Lambda - Making LPT changes for deploying and executing the tests in the pipeline approval workflows. - Synthesising the results in AWS Cloudwatch - Project: Proactive Outreach - UI and Service Integration Test Setup - Proactive Outreach (PO) is a program where the Customer Service Associates (CSAs) proactively monitors on-road exception events like Unable to Access (UTA), Unable to Locate (UTL), Business Closed (BC) and takes appropriate actions like reaching out to customers or performs research to resolve the underlying issues involving shipment notes history, access codes, business hours etc. - This project contains UI and Backend Service components as listed below: - Proactive Outreach Manager UI Pages - Built on top of Goa - Preach Service - I was tasked to Setup UI automation tests for Proactive Outreach Manager UI Pages
• I've used the same strategy as other Goa pages like DCLP and RCLP and incorporate these tests in the very same test package separating the execution file (testng.xml). - Adding to this, I was also tasked for setting up the Service Integration Tests for PreachService
• This service was onboarded with CloudAuth enabled security to which I was fairly new
• I had to learn on building the client with CloudAuth.

• Project: Migration from CSSM to Amazon Moment.
• Amazon Moment is a new tool which replaces Customer Service Schedule Manager (CSSM) and CSSM Mobile, and was built based on feedback provided by associates that the current interface was over complicated and some portions were no longer relevant
• Amazon Moment Integration tests were initially set up for in team use only
• Our goals with Workforce Management is to achieve FullCD and enable other teams across the org start consuming the test utilities starting from Day 1
• Since integration tests play a major role in getting to Full CD, they had to be reengineered in order to make it easy for other teams to set them up.
• Responsibilities: - Re-engineered the existing integration tests to be usable by other teams. - Developed a common library of utilities which include common features such as, navigating to sign in page, signing in, navigating to home page which could be used by any other teams. - Documented the process to create new integration tests and the process of integrating them to the pipelines. - Utilities in the WorkforceManagementUITestCommons package includes: - Sign In logic - Password based authentication support
• Retrieves credentials from Odin. - Global Identity (Cookie based/Password less) Sign In logic with system account - Service calls for UI automation tests made easy - Any service call can be done just adding the service name to the Client builder class. - iOS browser clean-up utility - Test Class - contains the core logic for signing in, retry failed tests and description of the test. - Project: Amazon Moment Automation - The UI for Amazon Moment was reactive enough to be scaled any device like mobile, tab and desktop
• The automation testing spanning across multiple devices and multiple browsers was a challenge
• Also, the major pain point during the testing was, the input for enabling the UI elements in Amazon Moment has to be provided in CSSM (being deprecated in the favour of Amazon Moment)
• This test scenario was super complex to work with
• It required two different front-end applications which share the same backend service to enable hidden elements of Amazon Moment pages
• Due to this blocker we were testing this manually every time
• Automating this test scenario along with the execution support on multiple devices/Operating systems and multiple browsers was challenging. - Setup the Test Automation Suite for both Mobile(iOS & Android) and Desktop platforms. - Evaluated most popular UI Automation Frameworks being used across Amazon and arrived at Diamond toolkit as the Framework to be used for my Tests. - Designed the Test Automation Code in such a way that demonstrates 'Write once, execute anywhere'
• The test once written can be executed on Mobile and Desktop platforms. - Since the mobile automation execution needed real devices, I have worked with the ARMED team and onboarded the ARMED device pool for running my tests for Android and iOS triggered from my team's ToD Worker environment. - Onboarded PULPO to enable cross browser testing. - Setup the common service call utility which is scalable and generic enough to be reused by all the three of Workforce Optimisation teams by consuming the utilities. - Ensured this service call was made before the test execution so that the required UI elements (OT/VTO postings) are available in Amazon Moment by the time the test class is invoked for these test scenarios. - Added the utility to pick the configuration like Domain and Realm based on the values specified in the build properties

• Project: Migration of Integrated Tests from CSTechWebstore to SellerCSWebsite
• Project Description:
• Integration Tests for SellerCSWebsite earlier were running on CSTechWebstore platform based on Graphite Automation Framework with package named CSCentralIntegrationTests
• These tests were placed in WebsiteBetaGamma pipeline against the new incoming CSC changes
• Due to the deprecation of Webstore platform (deprecation notice), the integration tests were removed from the pipeline and were shut down for a significant amount of time.
• Later based on GoaIntegrationTests reusable packages, I have came up with new Automated Test package SellerCSIntegrationTests build using Carbon Automation Framework
• This decision have unblocked us from running IntegratedTests on BetaGamma pipeline.
• Here's the list of Integration Tests that I worked, and are currently running in CSTech's Website-BetaGamma pipeline - Project Name: CSCentral Preprod Dashboard - Project Description: - CSCentral Preprod Dashboard (Website Link), a Python Flask based internal website was created to track the usage of CSCentral specific to Gamma stage.It had the statistical data representation view in the Home Page which displays the histogram with the highest number of page access details
• Another views like Gamma Usage, Gamma Workflows and Gamma Contact Clicks. - Later, I've added the additional views to track the data for CSCentral Preview Stage which are Preview Usage, Preview Workflows and Preview Contact Clicks. - Project Name: Gamma-Preview Program and Regression Testing for Customer Service Technology - Project Description: - Major part of regression testing is done based on the feedback from Gamma-Preview Testers spread across the network at a count of 400 active testers
• These testers cut a ticket to report the bugs whenever they find something deviated from the actual CSC software
• The QAs validate the bug reports - try to find the root cause and then pass it to developers for a fix and retest to verify if the fix works. - To execute the entire program, the following steps are involved: - Recruit Testers - Handpick/Manager's recommendation/Voluntary - Train/Explain how to report bugs and significance of each bug they report. - Manage/Maintain Testers - To track the testers, we need to be in constant touch with them via communicator, email or meet them in person
• CSAs change the role very frequently based on the business requirement, then we need to recruit new testers to backfill. - Regression testing is carried out in Preview CSC on the week prior to the release day of SellerCSWebsite to ensure that the critical functionalities of CSC aren't broken before the release as there is a chance of breaking the Production CSC leading to Sev-2 Impact. - Earlier, the Regression Testing used to be done based on GEOs, but now we have minimized the Regression tests to minimum which would add more value
• Removed several items from manual regression testing based off criteria determined by Team