SUMMARY:

• Hands on Experience on Performance Testing Tools like HP LoadRunner, HP Performance Center, New Relic, AWS Cloud Watch, Jvisual VM, Perfmon. HP StormRunner Load, Sumologic, testing applications built on Docker containers and managed through Kubernetes, Datadog, Apache Jmeter.
• Driven many projects in the previous account being the only person working for the Performance Testing activities starting from activities like Test Requirements Gathering, brain storming sessions with Business Users and project stake holders for understanding Performance Requirements, Creating Test Plans, Creating LoadRunner scripts and effectively conducting various performance tests like load, stress, endurance, volume
• Great hands on Performance Testing and Engineering experience working on AWS Cloud deployed applications.
• Experience in LoadRunner scripting for Web http/html, web services, REST api level performance scripting and execution,
• Writing and developing Custom C code in loadrunner scripts.
• Able to analyze and find out system performance issues after conducting the performance tests.
• Vast experience on server monitoring tools like New Relic, AWS Cloudwatch, JVisualVm, I3 Monitoring, Perfmon, Datadog, Web Page Diagnostics, etc.
• Experienced in Deep - down analysis using New Relic and Amazon Web Services Cloud Watch console for application performance bottlenecks.
• Hands-On experience with industry standard defect tracking tool JIRA, Confluence.
• Used MySQL Workbench and Valentina Studio for DB Querying
• Effective Communication Skills and problem-solving capability for critical application performance issues.
• Production Critical User Metrics reporting (weekly) and monitoring (daily)
• Prior experience with JVM Garbage collection principles, UNIX, Python (learning currently)
• Currently preparing for AWS Certified Solutions Architect Associate .
• Served at Customer onsite facing roles at London for a Swiss Bank Client and currently US based Banking, Media & Telecom clients.

SKILLS:

• PerfMon - Performance
• Monitoring Tool
• HP LoadRunner
• Apache Jmeter
• Performance Testing
• HP Performance Center
• Sumologic
• JVisual VM
• AGILE SDLC
• AWS Cloudwatch Console
• Performance Engineering
• New Relic Application Performance Management Tool
• Amazon Web-Services
• DataDog Monitoring Tool
• HP StormRunner Load
• MySQL WorkBench
• MEDIA AND ENTERTAINMENT, BANKING AND FINANCE, BANKING - CORPORATE BANKING, BANKING - CONSUMER BANKING, BANKING - RISK AND COMPLIANCE, SECURITIES

WORK EXPERIENCE:

Confidential

Lead Engineer - Performance Testing & Engineering

Responsibilities:

• Understanding the Business application Performance Non-Functional Requirements in an AGILE SDLC model through attending Sprint Planning meetings, daily Scrum calls, Backlog grooming calls.
• Single point of contact for Co-ordinating and performing the delivery of Performance Testing end to end tasks for multiple application micro-services.
• Handling and leading the efforts for delivering Performance Testing End to End tasks for multiple micro-services like Assess Authoring, Assess Delivery, Assess Scoring, Assess Multi Media Services, Ensuring smooth Integration of External Confidential applications with the above Micro-services from application Performance standpoint.
• Designing Performance Testing Approach for each application Release, deciding on the number of application critical Performance Testing business flows in consultation with Application architects.
• Estimating the time and efforts required for each of the critical Business flows Testing and delivery.
• Creating automated Performance test scripts using industry standard tools like HP LoadRunner for the identified application performance test requirements and critical business flows.
• Designing Performance Test Scenarios in HP - ALM Performance Center and Microfocus StormRunner Load tool that replicates the expected targeted production workload to be performance tested.
• Executing various Performance tests like load, stress, endurance tests to ensure the application meets the defined performance SLA's and stability and reliability requirements before deploying to production Environment. In Case of a new application functionality OR a new service to be developed for the first time => conducting baseline and benchmark performance tests to capture initial performance testing metrics for those new services that will help for comparison in later releases.
• Deep Drill-down analysis of the various performance tests conducted with the help of a) HP ALM results b) generated test logs from HP ALM Performance Center and Sumologic tool c) application performance monitoring tool New Relic to identify issues with various application tiers of web, app, or database d) AWS (Amazon Web Services) Cloudwatch management console to monitor and understand the server metrics and server resources utilization like CPU, memory, during executed performance tests.
• Load Test data management by writing and using DB Stored Procedures for data clean-up.
• Monitoring the Production systems - WEB server, Application server and Database server tier everyday for all the micro-services and Analyzing infrastructure lated resource usages slowness with Production systems
• Monitoring of overall quality and timeliness of performance testing deliverables.
• Engaging Application Architects and Site Reliability Engineering Support teams in case of any issues observed with underlying Application Infrastructure for its timely resolution.
• Documenting the executed performance test results and analysis in Confluence for each software release and reporting the same along with performance improvement recommendations to business key stakeholders like product owners, developers, solution architects.

Confidential

TEST ENGINEER

Responsibilities:

• Understanding Application non-functional Performance requirements by attending Sprint Planning meetings.
• Based on the understanding of the application performance requirements - for the identified critical application business flows => creation of API level Load Runner and or Apache Jmeter automated test scripts.
• Designing the Test Scenarios in HP ALM Performance Center to replicate and test the expected production workload.
• Executing various Performance tests like load, stress, endurance tests in HP ALM Performance Center to ensure the application meets the defined performance SLA's and stability and reliability requirements before deploying to production Environment. In case of api's getting released newly => conducting baselining and benchmark performance tests.
• Analyzing the performance test results from the various conducted performance tests through Performance Center logs, Sumologic tool, New Relic APM tool, AWS Management Console.
• Documenting the performance test results with analysis from each individual conduced performance tests in Confluence and reporting the same with performance improvement recommendations to business key stake holders.
• For the identified performance issues during the performance tests creating bugs and tracking its progress in defect management JIRA tool with the help of application team for resolving the same.
• Providing the performance sign-off after the resolution of all the critical performance issues.

Confidential

TEST ENGINEER

Responsibilities:

• Understanding application performance Business Requirements from the Project Business Team.
• Devising the Test plan and the test strategy and the work-load model based on the business requirements.
• Creation of Test Plan and Workload model.
• Creation of 7 LoadRunner scripts.
• Execution of Load Tests from 4 global regions using HP Performance Center.
• Sharing the Test Results and analysis reports with all stakeholders.
• Analyzing Performance test results and identifying potential application performance bottlenecks and creating performance defects for the same and getting them resolved verified and re-tested.
• Test data setup activity for the Swiss based servers is done by the other person based in Swiss region due to client sensitive data access issues.

Confidential

TEST ENGINEER

Responsibilities:

• Test Plan and Work Load Model Creation.
• Understanding application performance based Business Requirements for the RAVE application.
• Devising the Test Strategy based on the business requirements.
• Creation of 10 Load Runner scripts for the identified Business Critical scenarios.
• Load Test Execution with 1000 concurrent users test using HP ALm Performance Center tool.
• Reporting the application performance bottlenecks and issues for Dev team fixing and later re-testing the performance fixes.

Confidential

TEST ENGINEER

Responsibilities:

• Test Plan and Work Load Model creation.
• Creation of 49 Complex Load Runner Scripts.
• Test Data Setup for 1000 users in the system, assigning roles, making SQL entries, etc.
• Load Test Execution for 1000 users load test using HP Performance Center.
• Monitoring using Web Page Diagnostics.
• Nagios monitoring of the Testing Environment Servers during the execution of performance tests and observing and identifying any potential performance bottlenecks with the Testing Environment Server resources.

Confidential

TEST ENGINEER

Responsibilities:

• Create Performance Test Plan on the basis of expected application non-functional performance requirements.
• Create LoadRunner scripts for the identified critical application business flows.
• Executing Load Tests with concurrent multiple user loads as per the expected Production user-loads.
• Analyzing the Performance Center graphs and reporting SLA breaching transactions and other performance issues found during load tests.
• Creating a Performance Testing cycle Analysis report.
• Sharing updates daily and weekly with the client team on the progress of the Performance testing.

Confidential

TEST ENGINEER

Responsibilities:

• Doing Load Runner Scripting on Web-Http/Html protocol
• Working on scripting of Https secured applications using SSL s using Load Runner software.
• Should execute Load, Stress and Endurance Tests on software applications using HP ALM - Performance Center 11
• Writing Performance Test Plan, Performance Test Strategy document and doing performance testing estimations.
• Creating Performance Analysis reports and for identifying the possible performance bottlenecks.
• Working on JAVA / J2EE and Perfmon performance counters and the respective server analysis.
• Sending Daily Status Reports to client everyday on the everyday Performance Testing status.
• As a part of this project I have created 2 Load Runner scripts for MDM Performance testing.
• I have executed these 2 scripts which covers the 6 User scenarios in-scope with 18 user load to test the application performance.
• Also I worked on POC (Proof of concept) to create Load Runner scripts for Adsensa application which was developed using Google Web Toolkit and which makes use of gwt encoding mechanism to encode the server responses and the http requests are made using json.

Confidential

TEST ENGINEER

Responsibilities:

• Create Performance Test Plans on the basis of expected application non-functional requirements.
• Create LoadRunner scripts for the identified critical application business flows.
• Executing Load Tests with concurrent multiple user loads.
• Analyzing the Performance Center graphs and reporting SLA breaching transactions and other performance issues found during load tests.
• Creating a Performance Testing cycle Analysis report.
• Sharing updates daily and weekly with the client team on the progress of the Performance testing.

Confidential

TEST ENGINEER

Responsibilities:

• Creation of Load Runner scripts in Web-http/html protocol to measure the performance of the Web-Services. In this particular activity I automated the various User action http requests and collection of server responses from server using Load Runner. I have used the HP Load Runner software for automating the same WSDL soap request and responses.
• For validating the server responses we have made use of Load Runner’s in-built functions to validate the right server responses in Load Runner eg. There were a total of 7 web scripts that were performance tested. Execution of Load Runner scripts in HP ALM Performance Center 9.5
• I had executed many load tests with varied number of Virtual users in Performance Center.
• I had created Performance Tests wherein I have applied the expected used loadon each user action created as required when the application will go live and as requested by the client team. I have successfully run a lot of performance load tests to test the application performance. After the tests are executed successfully I have analyzed the performance testing report and results which contain how much time each transaction took to execute. After successful completion of each load test, I analyzed each transaction and have checked as to many transactions breach the expected SLA.
• Monitoring of Servers using I3 Mon monitoring tool and by accessing the database and server logs
• After successful completion of performance tests I have identified the possible performance bottlenecks that were uncovered by the execution of load and performance tests like highly utilized CPU Usage, heap memory issues, shortage of idle threads in execute queues, java methods high service timings, JDBC access issues, Connection pooling issues, database indexing issues, memory leakages, major garbage collection running on the java virtual machine, SQL’s consuming a lot of time on the server, etc. and many such performance bottlenecks were identified.
• As a part of this CLM performance Testing we have executed 4 Load Tests from the regions of New York, London and Singapore and Zurich.

Confidential

TEST ENGINEER

Responsibilities:

• Creation of Load Runner scripts in Web-http\html protocol to measure the performance of the Web-Services. I used the HP Load Runner software for automating the same WSDL soap request and responses.
• For validating the server xml responses we have made use of Load Runner’s in-built functions to validate the right server responses in Load Runner eg. text find on web page which helps in validating the right page content from the server response. There were a total of 7 web scripts that were performance tested. Execution of Load Runner scripts in HP ALM Performance Center 9.5
• I had executed many load tests with varied number of Virtual users in Performance Center. I had analyzed the performance testing report and results which contain how much time each transaction took to execute.
• After successful completion of each load test, I have analyzed each transaction and have checked as to many transactions breach the expected SLA.
• Monitoring of Servers using I3 Mon monitoring tool and by accessing the database and server logs
• After successful completion of performance tests I had identified the possible performance bottlenecks that were uncovered by the execution of load and performance tests like highly utilized CPU Usage, heap memory issues, shortage of idle threads in execute queues, java methods high service timings, JDBC access issues, Connection pooling, issues, database indexing issues, memory leakages, major garbage collection running on the java virtual machine, SQL’s consuming a lot of time on the server, etc. and many such performance bottlenecks were identified. These issues were reported to the development team or to the Architect team for them to tune the identified performance areas.
• I encountered some HTTPS security issues while scripting the application using Load Runner 9.5. So I raised those issues with HP support team and after the suggestion from HP team to install the latest patch of Load Runner.

Confidential

TEST ENGINEER

Responsibilities:

• I had worked on CDDS project in Credit-Suisse account for 5 months with hands on experience on Load Runner Scripts preparation, designing Performance Scenarios in Performance Center, Execution of the Performance Scenarios in Performance Center, analyzing the results through Analysis tool of Load Runner.
• I had used Web-Services protocol for Scripts preparation and have also worked on HTTP/HTML protocol while working on another project in the same account.
• I had also prepared the Performance Test Strategy Document for the performance testing phases and also prepared the Work-Load Model according to the Client's expected Non-Functional Requirements to calculate the user load on the various performance scenarios during performance tests execution.
• I was ed Feather In My Cap for performing an excellent job in Performance Testing for Phase-1 of our project. I was the only person performing all the Performance Testing Activities in our project.

Confidential

TEST ENGINEER

Responsibilities:

• I was involved in designing and writing test cases for 2 modules namely Agreement Management and Data.
• I was also involved in reviewing the test cases written by my team members.