An Automated approach towards Dev-Ops based continuous Regression Testing for SAP Landscapes Main Author - Navaneetha Kowdle (Associate Director) Co – Author - Akshay Mullick (Consultant) Cognizant

Abstract Navigating the complex digital landscape demands an effective testing strategy. Many of the world’s largest implementers of SAP are continuously looking to improve the effectiveness of an already mature QA organization. Regression testing efficiency can be improved to a great degree using effective impact analysis tools. However, in the quest for more agility commercial tools often fall short. Enterprises can significantly reduce test cycle time by using customized Test-ops solutions to achieve continuous regression testing.

Key Highlights Comparative Study of Impact Analysis tools available in Market and why SAP’s impact analysis tool – BPCA (Business Process Change Analyzer) is recommended. Solution Overview on how to use existing repositories, resources and tools to build automated solutions with minimal disruptions. Insights into the best practices, implementation challenges and workarounds to successfully implement BPCA. Description of how BPCA can be used to develop Test-Ops Solutions by implementing seamless end-to-end automated regression testing using a “Shift-Left” paradigm. Real success stories on test effort saving of up to 70% for each regression cycle.

Erstwhile approach Vs Impact based approach Optional Scenarios fragile (dependency on skills of individuals) Baseline Testing Driven by business critical scenarios covering core processes Understanding the changed Objects Limiting Test Scope Normal RT Scoping : Impact based RT Scoping : Regression Test Scope “Baseline” “Gap Identification” will identify Gaps that our RT Capability misses and triggers test case creation of those before RT cycle

Benefits of Impact Analysis Advancing Benefits Through Test-Ops Targeted Testing Reduced Effort Increased Resilience Faster Time to Market Reduced Cost Early Defect Detection

Why BPCA (Impact Analysis Tool) for SAP BPCA is a part of SolMan Suite and free to use. Provided a means to make use of existing Test repository to build a blueprint, thus providing a 1-1 mapping. More granular than other tools compared, thus providing finer impact ( Subroutine/Form level). Features such as configurable Test Scope Optimization / Multiplicity parameter to define extent of testing Advantageous in building customized solution for continuous testing

Implementing BPCA based RT– Key Steps Business Blueprint Set up of business process hierarchy Business Requirements TBOM Creation (Static/Semi-Dynamic/Dynamic) CHARM Change Document information Transport Information Business Process Change Analyzer Impact Analysis Test Scope Optimization Multiplicity Parameter Connection Setup Test Planning &Setup TAO/UFT Scripts Re-structuring Requirements Mapping Test Lab Creation Test Execution Impacted Automated Test Scenario Execution Impacted Manual Test Scenario Execution Defect Tracking Defect raised and tracked for failed scenarios

Regression testing – Impact based approach BPCA & TSO Executed with Transports collected from CHARM Developer implements the change and release the transport BPCA & TSO Change and Transport information flows to CHARM S7D4716 S7D4716 S7D4717 QA Environment S7D4713 S7D4714 S7D4712 HP Quality Center S7D4716 Pre-Prd Environment S7D4716 S7D4716 Test Lab created of impacted Scenarios after TSO from BPCA Automated Test Scenarios selected and executed in Pre-PRD

Pain Points encountered during BPCA implementation Substantial initial effort for dynamic TBoM creation. OSS Notes for enabling TBoM creation (auto and manual) – ended up as guinea pigs TAO scenarios restructuring – PFA consolidation etc. Need to review HP ALM structure in order to align with Blueprint / BPCA needs Technical Connection Setup with HP ALM Approach for auto TBoM creation for UFT scenarios Connections between SAP SolMan and Managed Systems

…limits speed and flexibility Focus on testing „new“ functionality Taking it Further – Pioneering work Increasing Test Coverage Continuous RT – adaption of Shift Left approach using DevOps “The V Model” “Shift Left” Gate 3 Regression testing ensures that a change or fix has not caused faults in unchanged parts of the system. Gate 2B Regression Test Light Regression Test Gate 0 Integration testing ensures that the e2e process as described in the design documents function as described. User acceptance testing ensures that changes meet the business requirements. - Business Requirements Gate 1 Gate 2A User Acceptance Test Gate 0 Gate 3 Gate 2B Functional Design - Business Requirements Regression Test Integration Test Cycle 1 / 2 Gate 1 Gate 2A Technical Design User Acceptance Test Functional Design H/H H/H Unit / Component / Assembly Test …turning into Continuous RT… Integration Test Cycle 1 / 2 Technical Design H/H H/H Build Unit / Component / Assembly Test …limits speed and flexibility New or changed requirements are brought to production by projects. Fixes to incidents and problems are brought to production by application maintenance. Build …will enable Fast Track Deployments not compromising on resilience finally resulting into Continuous Deployment… Focus on resilience Focus on testing „new“ functionality

Enterprise DevOps -Motivation and Guiding Principles Speed-up of go-lives of Enhancements / Innovations Cost reduction through higher degree of automation Much earlier detection of defects from regression tests Guiding principles Continuous development, regression testing and deployment. Monthly releases – mid-term goal: 2 weeks. Reduced System Landscape with max. 4 systems: DEV, QAS, Pre-PRD, PRD. Agile development approach replacing traditional waterfall approach

Continuous Automated Regression Testing BPCA & TSO Automated Inbuilt Mechanism Automated BPCA Execution Manual Process Test Data Solution S7D4716 Automated Test Lab Creation Manual Process S7D4717 QA Environment S7D4716 S7D4713 HP Quality Center S7D4714 S7D4712 Auto scenarios Automated Test Execution Manual Process Automated Test Selection Manual Process

Benefits seen post implementation Test Coverage Gaps identified which are not covered under Baseline Test Scenarios. Gap Fulfillment increased test coverage by 15% yearly. Accelerated Approach Shortened overall Release Cycle window from 4weeks to 3 weeks. Defects are caught earlier in Release Cycle. Cost Save cost by engaging less testing resources due to targeted testing. Fast ROI within 2-3 Monthly Release Cycles Tangible Benefits Up to 60% reduction in testing effort. Brought in 25% more agility which helps in faster “Time to Market”.

References & Appendix

Author Biography Main Author Co - Author Navneeth Kowdle is an Associate Director  with the  Process & Quality consulting division ( a part of Cognizant Business Consulting group). In this capacity , his role entails overall management of  PQC practice in the Communication ,Media and Technology space, in addition to personally  getting engaged with customers in providing consultancy services in niche  areas of Quality Assurance such as DevOps, Business Process Testing , QA transformation strategy etc Main Author Akshay Mullick is working as an Consultant  with the  Process & Quality consulting division ( a part of Cognizant Business Consulting group). My role is to act as a bridge between business and technology for client and propose solutions which addresses their problem statement. My area of expertise is Agile, Dev-Ops, Change Management, Tools & Automation around Impact based testing Co - Author

Thank You!!!