Welcome!

Microservices Expo Authors: Derek Weeks, Elizabeth White, Gopala Krishna Behara, Sridhar Chalasani, Tirumala Khandrika

Related Topics: Microservices Expo

Microservices Expo: Article

ChoicePay: Rising above the SOA Testing Challenge

SOA testing doesn't stand alone

ChoicePay has embarked on a strategic Web Services-based SOA initiative as part of its ongoing effort to improve customer and partner service. To meet its service improvement objectives, ChoicePay builds reliable and robust Web Services. It continues to enhance its service objectives without compromising overall quality through short, iterative, and demanding Web Services testing cycles.

Background
ChoicePay handles electronic bill payments for some of America's largest companies. Starting operations in 1996, it was a pioneer in the Electronic Bill Presentment and Payment (EBPP) industry and is recognized today as providing one of the most comprehensive suites of payment channels and options in its class.

ChoicePay's adoption of Service Oriented Architecture (SOA) stems from its continuous effort to improve service for its clients. One of the many SOA-based Web Services launched by ChoicePay enables centralized account number validation across all of its bill payment clients, encapsulating hundreds of masks, algorithms, and rules intelligently. As with other systems it has developed, this Web Service went through a meticulous design and implementation process. The intended goal was to provide a service that would cause minimal friction when integrated into a client's IT infrastructure. To reach this goal, the developers had to design a flexible service that would be readily consumed by multiple companies with diverse hardware and software platforms, operating systems, and programming languages. The SOA developers also had to ensure that the services were robust and reliable, which meant that the QA team had to ensure that all operations exposed by the service were thoroughly tested with a large set of data permutations. And for ChoicePay's Web Service, these rigorous and broad testing requirements had to be addressed in a span of only a month.

How ChoicePay Did It
"Testing a new function based on Web Services with global business visibility and produced on a tight schedule,posed a twin challenge for us," ChoicePay CTO Keith Fulton explains. "Throwing more bodies at the problem wasn't a viable solution. Our implementation required intelligent tools and techniques."

When Fulton initiated the SOA testing plan with ChoicePay's software QA team, he first identified the key objectives in order to roll out the service:

  • Verify correctness and an exact one-for-one match with the functionality the service was replacing and centralizing, which involved testing several thousand business cases and validating the results
  • Boundary conditions were tested to ensure the robustness of the Web Service
  • Each operation exposed by the service had to meet specific performance metrics
  • Ensure that the service met interoperability criteria since it was to be consumed by multiple companies

    The recognition of these objectives introduced several issues:

  • All of the objectives had to be met with limited human resources
  • Creating repeatable baseline tests was required so iterative regression testing could be done
  • The bug reports that were generated had to be precise and easily understood to ensure that developers could create quick fixes to make the project timeline as short as possible
Meeting the Challenge
The initial task was to select the right testing technology to quickly meet the objectives set by Fulton and overcome any hindrances. This included rapid deployment and a limited time for testers to come up to speed with the new product. The criteria to select the right testing technology was based on it meeting current testing objectives, being easy to use, cost-effective, and extensible for future testing scenarios. From an extensibility perspective, ChoicePay wanted to select a testing tool that would fulfill the following core functional requirements: (see Table 1 )

The goal behind these requirements was to find a unified SOA testing technology that would be reusable across multiple IT groups during pre-deployment and post-deployment. Also, given the tight testing schedule, it was important for ChoicePay to have an easy-to-use technology that didn't require a significant time investment for training. The testing team didn't have time for boot camp-type training.

After evaluating SOA testing technologies from several companies, ChoicePay selected Crosscheck Networks SOAPSonar Enterprise. ChoicePay was most impressed by the ease-of-use and rich functionality that not only addressed ChoicePay's stringent testing criteria, but also gave the team immediate productivity improvements . It took less than an hour for the ChoicePay testing team to become effective using the product.

Besides the ease of use of SOAPSonar, the support team at Crosscheck Networks was responsive. Each issue raised by testers was immediately discussed and alternatives given without impacting the project timeline. This allowed full and complete testing during a short time frame for the implementation. "We rely on agile competitive partners in technology and Crosscheck Networks proved to be exceptional," Fulton said.

As the testing plan was taking shape, ChoicePay continued developing effective techniques to maximize their utilization of SOAPSonar. The first technique focused on test-case usability. Borrowing from SOA's emphasis on reuse, ChoicePay's QA team created a set of test cases that could be reused across multiple SOA testing functions such as functional regression, performance, and interoperability.

The second technique adopted by ChoicePay was to leverage external data sources to dynamically parameterize SOAP requests as well as expected SOAP-response success criteria. This technique enabled the QA team to conduct full regression tests across thousands of test cases. Figure 1 illustrates the basic setup and highlights different components that played a role during rollout.

In Figure 1, SOAPSonar enabled the testing team to create coarse-grained and fine-grained filters to verify the integrity of SOAP responses from the target Web Service. The team was able to create filters based on both HTTP response codes and specific XML elements within SOAP responses. The ability to create fine-grained filters enabled the testing team to quickly identify successful and erroneous responses. Sorting data issues from application issues was simplified by using these filters. Rich reporting also played a key role in facilitating rapid bug fixes by development. Without accurate reporting, the team wouldn't have been able to convey the bugs to the development team and identify whether the issue was code-related or database-specific.

Next Steps
After its initial success, ChoicePay will continue performing real-time integration with clients where critical business processes will be interdependent. "We will use SOAPSonar not only internally, but also to certify our clients' Web Services on a daily basis to ensure there aren't changes or upgrades on their side that impact our ability to do business," explains Sandee Wagner, QA lead at ChoicePay. The plan here is to consume multiple Web Service Definition Language (WSDL) files into SOAPSonar and schedule a test on a daily basis where multiple test cases would be run against remote client Web Services, and reports would be compared from a previous day's run. Figure 2 illustrates the technique to test the customer's Web Services.

Summary
After successfully implementing the test plan, ChoicePay's QA team was able to achieve the project's goals and provide confidence that the Web Services were adhering to functional, performance, interoperability, and security requirements.

Fulton is confident they have gained considerable experience in the last few weeks with timely Web Services-based rollouts, saying, "Our experience with SOAPSonar has given us the ability to provide best-in-class reliability in highly complex, real-time distributed systems across multiple enterprises." Some of the valuable lessons learned during ChoicePay's development and release exercise include:

  • Minimizing the impact of Web Service complexities through the effective use of good testing tools
  • Developing test cases that are readily extensible through the use of parameters and external data sources
  • Reusing key validation criteria iteratively through a project's lifecycle
  • Create ongoing controls to monitor live Web Services where dependencies exist
For ChoicePay, SOA testing doesn't stand alone. SOA testing spans complex internal and external services in different phases and versions of the service lifecycle. For ensuring business growth through customer and partner integration, ChoicePay has made reliable and robust SOA a core blueprint of its corporate strategy.

More Stories By Salman Akhtar

Salman Akhtar is the CEO and Co-Founder of Techlogix and has over 15 years of industry experience. Salman holds two degrees in Electrical Engineering from MIT.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
DevOps promotes continuous improvement through a culture of collaboration. But in real terms, how do you: Integrate activities across diverse teams and services? Make objective decisions with system-wide visibility? Use feedback loops to enable learning and improvement? With technology insights and real-world examples, in his general session at @DevOpsSummit, at 21st Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, explored how leading organizations use data-driven DevOps to clos...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things c...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?