Customer Success Story

Key Challenges: the system integration phase. At the Verifying Middleware completion of the development phase, : One of the key technical risks was ensuring they had exceeded the ROI by 68%. Interactions with SAP that the mapping and transformation logic in the middleware system was correct once Moving from Manual to Automated A Use Case in Service Virtualisation migrated. After reviewing options, it was Testing and API Test Automation determined that the most cost effective and reliable approach was to remove the Before the upgrade project, the team’s dependency between the middleware existing manual testing process was able and back-end systems by virtualising SAP. to keep pace with the rate of application This would provide a means of building updates. However, once the project was the switching logic within its Middleware fully scoped, it became clear that the component before the SAP interfaces were existing manual process would not be THE CHALLENGE available, as well as being able to repeat sufficient, considering the time required tests without the overhead of data setup and to set up data in SAP, waiting for SAP to A financial organisation was embarking teardown. be made available, as well as the number on a technology upgrade, involving of software iterations expected. SAP as its core replacement technology The organisation’s next challenge was to partner to migrate off its legacy backend justify the investment to change from a Virtualising systems. Wanting to leverage the existing manual testing approach (at the service layer), Middleware platform to seamlessly switch to an automated approach without end- The most obvious benefit of having service from old to new without impeding the to-end functionality. The ROI was a simple virtualisation was that the team could customer experience, the organisation metric that stakeholders could understand begin developing and testing against sought a solution that could provide them and relate to - defect cost avoidance. If they the new back-end systems’ anticipated with confidence in the changes being made could find 3 defects per operation during behaviour before those systems were within its Middleware system. the development phase, this would avoid actually deployed. a greater cost of resolving defects during

THE SOLUTION The organisation moved from manual to automated testing, adopting Parasoft’s Continuous Testing platform to create an automated test suite that could be run after each new build of middleware.

The most obvious benefit of having service virtualisation was that the team could begin developing and testing against the new back- end systems’ anticipated behavior before those systems were actually deployed.

Perfecting Software Additional benefits included: authentication issues with our data) and able to focus on testing what • They no longer had to wait to get the the test’s purpose was. test data needed for each test or to have the test data reconfigured to the • Since virtualisation required the desired state (for example, reopening team to replicate the behaviour of an account that a test closes so that the back end, this forced them to it is ready for the next automated test dig deeper into how the back end run). worked.

• They could easily mimic a broad set of • In one of the more complex back-end system response conditions systems, they worked with the (e.g., data variations, failure conditions, Middleware developer and the performance variations), which helped SAP developers to work out how them catch complex issues prior to the mapping would take place and deployment. were able to simulate a response from the SAP developers in • Since the virtualised responses were Virtualize to help the developer validated and consistent, the team to build the Middleware code knew that any detected problems correctly. with the response messages actually stemmed from an issue with the White Box Testing Application Under Test — not a back- end system update, reconfiguration, From a development perspective, it or failure. was not sufficient to simply validate the requests and responses were returned as • The team started building automated expected, but the internal orchestrations, tests for each SAP operation as the workflow and downstream output were associated middleware code was correct. The team integrated Parasoft’s being modified. Tests were defined event monitoring with the middleware with Parasoft SOAtest, which works system to inspect each message flow alongside Parasoft Virtualize in the and assert that the results were as Parasoft Continuous Testing platform expected.

• Backends that the application Outcome under test communicated to, but were not part of the testing scope, At the completion of the delivery the were virtualised to always give a team amassed an automated test suite successful response. This made tests that could be run after each new build more reliable (as these backends of middleware. The number of backends were sometimes unavailable or had virtualised amounted to 8.

ABOUT PARASOFT www.parasoft.com Parasoft helps organizations perfect today’s highly-connected applications Parasoft Headquarters: by automating time-consuming testing tasks and providing management +1-626-256-3680 with intelligent analytics necessary to focus on what matters. Parasoft’s Parasoft EMEA: technologies reduce the time, effort, and cost of delivering secure, reliable, and compliant software, by integrating static and runtime analysis; unit, +31-70-3922000 Perfecting Software functional, and API testing; and service virtualization. With developer testing Parasoft APAC: tools, manager reporting/analytics, and executive dashboarding, Parasoft +65-6338-3628 supports software organizations with the innovative tools they need to successfully develop and deploy applications in the embedded, enterprise, Copyright 2017. All rights reserved. Parasoft and all Parasoft products and services listed within are trademarks or reg- and IoT markets, all while enabling today’s most strategic development istered trademarks of Parasoft Corporation. All other products, services, and companies are trademarks, registered initiatives — agile, continuous testing, DevOps, and security. trademarks, or servicemarks of their respective holders in the US and/or other countries.