Resume

Amrita Mukherjee Email: adb49y@r.postjobfree.com

Ph: 210-***-****

Objective

Seeking a challenging, positive environment that encourages continuous learning and creativity, providing exposure to new technologies and simulates personal and professional growth.

Professional Summary: -

Over 10 years of experience as a Quality Assurance Test Lead / Quality Assurance Engineer, performing manual and basic knowledge of automation testing for client server and web-based application

Hands on experience with all phases of Software Development Life Cycle (SDLC) and Software Test Life Cycle (STLC) and also have Exposure to Agile process (RAMP) and methodologies

Well conversant with software testing methodologies including developing Test plans, Test scenarios, Test cases, Test procedures, Test reports and documenting manual and automation tests

Extensive experience in testing of large client server applications, Web based applications, E-Commerce Applications and Middleware applications

Expertise in project management skills by handling all meetings, data analysis, documentation and business reports

Hands on Experience in QC ALM 12.2 0(Test Case Management) and Team Foundation Server 2015(used for Defect Tracking and Review Process)

Proficient in using Microsoft Office tools and Well versed with SQL, PL/SQL queries to run the data integrity tests

Participated in internal and External Audits which happened for the Project

Effective Knowledge of Team Foundation Server 2015 and used TFS for Bug Reporting tool and Review tool

Full life cycle experience in Quality Assurance, including Black Box, system, integration, database, performance, GUI, Functional, Regression, Unit testing, User Acceptance, Smoke testing and Sanity testing of both client-server and web-based applications.

Involve in developing and maintaining Test Matrix and Traceability Matrix, and performing Gap Analysis

Knowledge of Ranorex 7.0 automation

Effectively involved in bug tracking, reporting reviewing and analyzing test result using Quality Center ALM 12.20 and knowledge of bug tracking tool TFS 2015 for reporting bugs to developer

Excellent communication and interpersonal skills with problem solving abilities, effective in working independently and an exceptional team player

Skills Summary

Quality assurance & quality engineering

Test Plans, Test Cases & Review Processes

Functional Requirements

Regression & Negative Testing

UI & Compatibility Testing

Data Interface & Migration Testing

Performance/Load/Stress Testing

Defect/Bug Tracking

Test Strategies & Coverages

PL/SQL—Database Testing

Report Testing

Alert Testing

Email Work Flow Testing

Technologies

Testing Tools

MS Visual Studio TFS 2015, Ranorex 7.0, Quick Test Pro (QTP), Selenium

Test Reporting Tools

Quality Center (QC) ALM12.20, Whizible SEM

Operating Systems

Windows 98/2000/XP/7/10, Unix

Database

Oracle, Microsoft SQL Server

Programming Language

SQL, PL/SQL, VB Scripting

Bug Reporting Tool

TFS 2015, Whizible SEM

Web Technology

HTML, XML

Certification: -

ISTQB Foundation Level Certified

Working Experience:

Worked in Persistent Systems Limited, Pune from 1st Nov 2006 to 1st Dec 2017.While Leaving the Job, my Designation was Senior Team lead. The Work includes complete Testing Process of the systems(both EIS and ERP Application)which are been developed,going for Audits, created User Manual for some systems for customers, created process documents for the team, giving support to the whizible tool and written Stored procedures, created reports and have little knowledge of Ranorex 7.0 for Test automation .

Projects Worked:

1. Client: Persistent System Ltd. (https://www.persistent.com)

Title: Audit

Role: Auditee

Duration: Every Quarter

Description:

External Auditors: E&Y, DnV and Internal Audit Team ISMS used to Audit Projects Every Quarter. They used to check the complete Process followed along with the documents which are placed in the correct release folder. Also they would check the previous Audit points if any.

Roles and Responsibilities: -

oCo-ordination preparation of all relevant documents by interacting with different agencies

oVerification of Administrative activities on ERP/ESG Systems.

oProvisioning/De-provisioning rights of team members

oRefer VSS/ Testing Documents/ESGQA Induction Pack for activities related to E & Y

2. Client: Persistent Systems Ltd

Title: EIS Applications

Role: Tester

Duration: 1st Nov 2006 to 1st Dec 2017

Description:

oEnterprise Service group is the group which used to develop Applications which will be used by all employees of an organization. Supports all day to day functions and management requirements. Lays down a process of operating between and within functions of an organization and vendors. There are many EIS applications which are still in use after procuring ERP Product. Some small applications are still developed. The existing application which were developed are been getting change request and based on the priority changes are been done.

oThere are many EIS Applications like Appraisal System, Hardware Software Procurement System, Travel management System, Visiting Card System, Training management System, Monthly Billing system, Invoice management System, Mentor mentee system, Reports, Attendance System etc.

Roles and Responsibilities: -

oAs we were following RAMP Process, so we used to have Monthly plan and Weekly plan. For Weekly plan we used to get requirement and do the testing process. Below mentioned tasks are done when the sprint was monthly.

oBefore Starting the requirement are created as Features in a Internal System known as Sarathi.

oFirst understands the requirement in terms of what to be tested & figure out the testable requirements. The requirements are been Tagged in the Monthly Sprint or Weekly Sprint.

oTest Plan will be created after Requirement Freezing has been done. In the Test plan we mention the Testing Strategy, Test Automation, Testing Resource, Testing Schedule and Test Execution Deliverables.

oUsed to write test cases along with the test data.

oThe Test cases are been uploaded in TFS for Review.

oAfter Internal review, then the test cases are been shared with the developers.

oThe test cases are been uploaded in QC ALM 12.20 for execution.

oAfter test environment has the changes then testing phase used to start. When any test case used to pass, marked the test case as Passed and when any test case use to Fail then in QC used to mark them as Fail and in the description use to mention Defect Id.

oIf the Build is not testable then the build is rejected with subject line as Sanity issue encountered.

oOnce the defect is fixed by development team then same test case can be executed and defect status is either changed to Closed or Reopen.

oTo check for the completion of the test we checked whether all the test cases are executed, all valid P1 and P2 defects are fixed and verified. After Satisfying the above-mentioned criteria, testing concluded mail should be sent and, in Sarathi the features, should be mapped to signed off.

oCreate Defect Summary report, Data Analysis.

oLessons learnt meeting is done and create lessons learnt document

3. Client: Persistent Systems Ltd

Title: ERP Applications (MS Dynamics 2009)

Role: Tester

Duration: 1st Jan 2011 to 1st Dec 2017

Description:

Organization had Procured Microsoft Dynamics AX software product as organizing was growing and internal system was not helping in this matter. This is one of Microsoft's enterprise resource planning software products. It is part of the Microsoft Dynamics family. Microsoft Dynamics AX contains 19 core modules. All modules were customized as per company policy and were thoroughly tested. Modules were Human Resource, Recruitment, CRM, Finance, Procurement, Order Processing, Projects, Projections, Resource Management, General Ledger, Account Payable, Accounts Receivable, Bank, Inventory Management and many more. RAMP process (This Process is in agile manner following SCRUM methodology) is been used.

Roles and Responsibilities: -

oAs we were following RAMP Process, so we used to have Monthly plan and Weekly plan. For Weekly plan we used to get requirement and do the testing process. Below mentioned tasks are done when the sprint was monthly.

oBefore Starting the requirement are created as Features in a Internal System known as Sarathi.

oFirst understands the requirement in terms of what to be tested & figure out the testable requirements. The requirements are been Tagged in the Monthly Sprint or Weekly Sprint.

oTest Plan will be created after Requirement Freezing has been done. In the Test plan we mention the Testing Strategy, Test Automation, Testing Resource, Testing Schedule and Test Execution Deliverables.

oUsed to write test cases along with the test data.

oThe Test cases are been uploaded in TFS for Review.

oAfter Internal review, then the test cases are been shared with the developers.

oThe test cases are been uploaded in QC ALM 12.20 for execution.

oAfter test environment has the changes then testing phase used to start. When any test case used to pass, marked the test case as Passed and when any test case use to Fail then in QC used to mark them as Fail and in the description use to mention Defect Id.

oIf the Build is not testable then the build is rejected with subject line as Sanity issue encountered.

oOnce the defect is fixed by development team then same test case can be executed and defect status is either changed to Closed or Reopen.

oTo check for the completion of the test we checked whether all the test cases are executed, all valid P1 and P2 defects are fixed and verified. After Satisfying the above-mentioned criteria, testing concluded mail should be sent and, in Sarathi the features, should be mapped to signed off.

oCreate Defect Summary report, Data Analysis.

oLessons learnt meeting is done and create lessons learnt document

4. Client: Persistent System Limited

Title: Support to Whizible

Role: Administrator

Duration: 1st Nov 2006 to 31st Dec 2011

Description:

Whizible SEM™ is a Services Execution Management solution. It helps service centric organizations to manage projects, processes and interactions between teams. It provides the critical information needed to take your strategic goals to successful completion.

Whizible SEM™ offers following strategic benefits…

Integrated Solution to manage the different components of your operations – project management, process compliance, resource optimization and knowledge components.

Visibility on the status of projects to internal stakeholders as well as your external stakeholders, the customer.

Productivity: Reduces administrative overheads, leading to operational efficiency and productivity.

Competitive Edge: Improved visibility and collaboration that enhance customer satisfaction

Resource Optimization: Manage your human resources – their time, skills and efforts, to achieve topline benefits.

Provides visual representation of critical operating parameters in the form of e-dashboards

Enables you to execute and track projects.

Two-way integration with MS Project

Information available at different organization levels

Helps with quality process compliance

Tracks the time, effort and skill sets of your resources

Allows you to capture and track issues and their resolution

Captures and tracks metrics on corporate and project levels

Helps you to manage help requests and support services

Provides a Knowledge Management system

Roles and Responsibilities: -

Having role as an administrator in the whizible.

Used to prepare reports and write stored procedures using SQL Server.

As per the requirement, created projects, Resource allocation, Changes to the end date

Education:

MBA (IT) in Information Technology from Symbiosis Institute of council for studies and research (S.I.C.S.R), Pune, India - 1ST Class (63%)

Bachelor in Science (Statistics) from Fergusson College, Pune University, India

1st class with distinction – 78.08%

Personal Information

•Nationality : Indian

•Work Authorization : H4 EAD, Valid Nov. 05 2020

•Gender : Female

Contact this candidate