SKILLS:

• Configuration Management
• Configuration Management
• CPG
• Distribution
• Functional Testing
• Regression Testing
• Retailing
• Software Engineering Tools
• Test Data Management
• Apparel - Promotions and discounts ( Retailing )
• CPG Basics ( CPG )
• Distribution Basics ( Distribution )
• Microsoft VSS ( Configuration Management )
• Mute Channel Commerce overview ( Retailing )
• Retailing Basics ( Retailing )
• Test Case Preparation ( Functional Testing )
• Visual Source Safe (VSS) ( Software Engineering Tools )
• Web based testing ( Functional Testing )
• Web based testing ( Regression Testing )

TECHNICAL SKILLS:

Systems worked on: Ecommerce, WCS, OMS, Retails inventory systems, iSeries 5250 etc. (hands on familiarity with SAP MM & FICO modules, WMS 2016)

Databases Worked on: DB2, SQL Servers, Oracle etc.

PROFESSIONAL EXPERIENCE:

Confidential

QA lead

Responsibilities:

• Requirements Analysis with Client IT team and Business users, Test Strategizing and functional requirement analysis, Project planning & tracking, Test Plan Design, client interfacing (IT Team and Business users) status reporting, pre - launch day in life testing, onsite-offshore co-ordination and leading the offshore team etc.
• I was hired as part of the R3 project QA Team and was the onshore QA lead for the MM Functional Module.
• IMM functional module included
• Being the QA lead I was responsible for the test script design, test data identification for all the test scripts, tracking the execution of the test scripts along with defect analysis and tracking.
• The entire testing phase was divided into 4 System Integration testing ( Confidential ) phases.
• All the test scripts were assigned specific Confidential cycles with individual test script carrying over into subsequent Confidential cycles depending on the nature of the defect encountered and the complexity of the condition under test.
• During initial phases of the Confidential cycles I was also working directly with Test Data Management team to identify the necessary files, control file data for every data set necessary for the test sets belonging to Confidential cycle.
• Day In Life in simple terms refers to processing one entire day data from production in the QA Test systems and validating the Confidential conditions with the available data.
• This approach enables the testers and UAT team to not depend on one set of data for any Confidential condition but a large pool of data. Such kind of testing also ensures the integrity of the functionality being validated.
• During the initial planning phases of the day in life testing I was responsible for identifying and defining all the necessary source files needed for the functionality process listed above.
• The approach was to have the source files restored in the QA systems from PROD backup tapes, extra necessary information through the series of the legacy iSeries jobs and interface them to the SAP QA test client for validation.
• I was responsible for defining the timings on the data loads, analyzing the extracted data in legacy to identify any issues & report defects, ensure the exact data is posted in SAP, work as a team to complete the test condition validation.
• Later phases of Confidential testing, project team took the decision to go with Early Install for the iSeries objects. The R3 legacy objects are designed specifically to feed data into SAP Clients, hence these objects were not having any direct impact on day to day process.
• The end point of the R3 legacy objects were independent files called as staging files.
• The records were stored in staging files and series of MQ jobs further downstream will enable the data to be interfaced over to SAP systems.
• This early install enabled the project team to limit data restore in legacy files and data extraction in legacy.
• After the early install of the objects were completed, my responsibility included validation of the data in staging files, required fields are populated according to the requirements, design and define the SQL queries to all the required data for one processing day (example a PO maybe created on one day and updated subsequently until the day of receipt, so the query should be able to differentiate the available records), maintain the SQL quires and execute & report the testing status once the data for one processing day was interfaced to SAP.
• After SAP R3 project went live, I was assigned to the IMM Functional support team where daily activities included working with IMM Business team to analyze the issues reported, provide technical support on Incidents and enhancement discussions, root cause analysis for daily business issues reported etc.
• In addition to the above I was also the functional point of contact for R3 Automation project and was responsible for designing the functional specs which helped the automation team to design the automation scripts for the MM functional modules.

Confidential

Technical Test Lead

Responsibilities:

• QM lead for Confidential team at client side, Requirements Analysis with Client IT team and Business users, Test Strategizing and functional requirement analysis, Project planning & tracking, Test Plan Design, client interfacing (IT Team and Business users) status reporting, onsite-offshore co-ordination and leading the offshore team etc.

Confidential

Technical Test Lead

Responsibilities:

• QM lead for Confidential team at client side, Requirements Analysis with Client IT team and Business users, Test Strategizing and functional requirement analysis, Project planning & tracking, Test Plan Design, client interfacing (IT Team and Business users) status reporting, onsite-offshore co-ordination and leading the offshore team etc.

Confidential

Test Analyst

Responsibilities:

• Requirements Analysis, Project planning & tracking, Test Environment Setup, Track open defects to closure, Participating in reviews, Quality Management

Confidential

Test Analyst

Responsibilities:

• Requirements Analysis, Project planning & tracking, Test Environment Setup, Track open defects to closure, Participating in reviews, Quality Management

Confidential

Test Engineer

Responsibilities:

• Analyze the Test Requirements and Test case planning
• Test case preparation
• Test execution based on planned test scenarios/ cases
• Design
• Test defect reporting by providing details regarding the defect, steps to recreate, severity etc.

Confidential

Test Engineer

Responsibilities:

• Preparation of Test scripts, Execution of Test cases, Reporting of Test Defects, Track open defects to closure, Participating in reviews, Configuration controller

Confidential

Developer

Responsibilities:

• Worked in major enhancements (RFAs) in the project and been a responsible back-up CC for more than 4 months.