Nov 2014 – Oct 2016 · 1 yr 11 mos

• My responsibilities include development of new features and stabilization of Enterprise Commerce systems with special focus on performance and security.

Jul 2011 – Nov 2014 · 3 yrs 4 mos

• Performance testing of multiple applications in licensing domain having both web and thick client architecture and using multiple technologies like web, wcf, wpf and appfabric.
• Roles and Responsibilities:
• 1. Planning performance test strategy and identifying performance scenarios.
• 2. Developing automated performance test at api level and on client side.
• 3. Measuring multiple performance metrics and analyzing the root cause of deviation.

Jul 2007 – Jun 2011 · 3 yrs 11 mos

• Working as Software Test engineer on MSIT e-Commerce Application
• Product Description:MSIT e-Commerce is a highly configurable worldwide platform which provides e-commerce capabilities including taxation, payment, fulfilment and reconciliation to Microsoft Marketing Programs and other campaigns.
• Roles and Responsibilities:
• Functional Testing:
• 1.Worked across multiple(10) releases of Order Management and emerged as SME on entire application with special focus on taxation, fulfilment and payment.
• 2.Utilized and evangelized Model Based Testing and other modern test techniques to improve test quality
• 3.Developed test harnesses to mimic consumer application using Webservices, AJAX, ASP.NET and C#.NET
• Performance Testing:
• 1.Utilized VSTT Load testing tools to perform performance testing in multiple releases
• 2.Applied performance modelling principles to identify performance touch points and design focussed test cases
• 3.Utilized SQL Profiler other tools to analyse and find out root cause of performance issues
• Automation:
• 1.Designed Automation framework for Order Management to automate ~2000 cases with following attributes
• a.Framework Independent:Implemented layered architecture to separate business logic testing from low level technology details.
• b.Automated Failure Analysis: Implemented AFA to identify and retry cases failed due to environment issues
• c.Generic UI handling: Key attributes like controlid, controltype and action were defined within the test data and hence no development was required even when large number of new controls were added
• d.Backend System Automation: Provided support for non-UI automation like – Data Feeds, Webservices, Database, Windows Service
• 2.Designed Windows Form Application to manage automation creation, execution and result analysis to provide easy interface to the testers
• Code Coverage:
• 1.Evangelized application of code coverage in testing by sharing expertise, creating best practices and ancillary tools.