Effective Performance Testing in Agile and DevOps Deepak Khatri Sr. Test Architect NIIT Technologies Pvt. Ltd.

Abstract Application performance is essential part of user expectation. Unexpected performance could have very high negative impact on business. Usually performance testing is started, once application has been developed and reasonable amount of functional testing has been done. In today’s rapid development environment, where we are more Agile, it is important that application performance testing should be started in early stage of the development in automated & integrated way. In Agile way of working or in integrated DevOps environment, it is essential to handle performance testing at unit, integration and system level. Proposed Best Practice is to demonstrate the Effective way of performance Testing in Agile and DevOps.

DevOps = {Agile Methodology + Shift Left Approach + Lean Testing} Fast, Automated, Time to Market Goals of DevOps: Fast and Contiguous Early and Often Test, Risk identification in same phase Time to Market Minimum Time wasted Low Risk Improved Code Quality + Shift Left : Early and Automated Testing + Lean: Remove Waste

“DevOps”, an Extension of Agile Methodology

Performance Testing Challenges in DevOps and Agile Identify the performance issues in Agile and DevOps is bit complex. Limited Time for testing. Low Priority : Functional validation have higher preference. Rather than identification, fixing of the performance issue required. Performance Engineering instead of Performance Testing. Performance can be validate at various level in project life cycle

Performance Testing in early stage and it’s Approach Performance of the application can be validated at various level of testing, which is not limited to system testing. Application performance could be impacted due to following factor: Application Code itself (Unit Level) Application and other external component and their integration (Integration Level) Infrastructure and configuration (Platform or System Level) Production scenario

Usual Architecture in DevOps and Agile

Performance Validation in DevOps

Where to Fit, What Profiling and Static Code Check for Performance UNIT Level System Integration Level Performance Monitoring Profiling and Static Code Check for Performance Performance Testing Performance Monitoring

DevOps Architecture Performance At Level, Type, & Tools Continuous Development Continuous Integration Continuous Deploy Continuous Test Continuous Delivery Continuous Monitoring Dev SCM Build & Integration Deploy Test Stage Production DevOps Architecture Unit Level Performance System Integration Level Performance Production Monitoring Performance At Level, Type, & Tools Static Code Analysis & Dynamic Code Profiling Performance Test Production Performance Monitoring Sonar, VisualVM, etc Jmeter, Grinder, OpenSTA, etc Nagios, Splunk,Perfmon, etc

Benefits Following benefit can be observed using performance testing in Agile and DevOps: Business application confidence Faster Time to market Performance issue identification in early stage Effort/cost saving Better user experience. Better Quality

Demo

Take Away Start Performance validation in early stage Choose right tool for the integrated Agile/DevOps System Automation for performance at various level Performance Validation Trigger on build, or on schedule Focus on performance engineering rather performance testing.

Bibliography http://www.softwaretestinghelp.com/devops-and-software-testing/ http://www.slideshare.net/ITRevolution/thursday-320-john-kosco-gb-final https://en.wikipedia.org/wiki/DevOps http://www.neotys.com/

Author Biography Total 15 Years of IT experience. Currently working as Senior Test Architect, with responsibility of Pre-Sales Tech Support, Delivery Technical Support, RFP response, mainly performance testing and engineering. Past 14 years of total experience in Software Engineering Automation Performance Testing and Software Engineering Tools. Qualification : MCA Certified Scrum Master, ISTQB FL Certification

Q & A

Thank You!!!