In Forbes’ recent article on the business drivers for test automation Peter Cohan wrote about Vantiv’s impressive achievements transforming testing to keep pace with Agile development:

Credit card payment service provider Vantiv is undergoing a “digital transformation” according to Sujit Unni, Vice President of IT at Vantiv. As Unni explained, “Vantiv is a more traditional market leader, processing 200 million to 300 million transactions per day — far bigger than a disrupter like Square which handles 10 million transactions annually. We have struggled with changing our IT development approaches from traditional to agile to DevOps. We used to take two weeks to develop code and three to six weeks to test using tools from Hewlett Packard Enterprise.”

Vantiv compared testing tools from its current vendor, HPE, with those from Microsoft Team Foundation Server (TFS) and Tricentis.

Vantiv chose Tricentis because it was more efficient. As Unni said, “Microsoft TFS allows for automation, but it’s just scripting. With Tricentis Tosca, quality assurance now happens continuously – without scripting, without programming. Our manual testers have become automation specialists.”

Want to hear details about how Vantiv  reduced their risk while accelerating time to market? Join the Digital Transformation through Agile Test Automation: The Vantiv Success Story webinar on April 26. Leaders from Vantiv and TCS will be sharing details of how they were able to:

  • Ensure faster, reliable, and predictable testing to support Agile transformation
  • Centralize regression testing and test data management across a collaborative enterprise-wide QA team
  • Achieve Continuous Testing with Continuous Integration
  • Reduce time-to-market and testing costs while ensuring superior customer experiences
  • Achieve 90% increase in business risk coverage and a 90% reduction in regression test execution time

Want a preview of their test automation achievements? Download the Vantiv Case Study now to learn how they tackled a number of common test automation challenges, such as:

  • Large regression suites could not be fully executed manually; even partial coverage took several weeks
  • Testing depended on inconsistent existing test data because creating new test data was too time-consuming
  • Tens of thousands of manual test cases in HP ALM were defined in ways that led to misinterpretation and inconsistent execution with unknown risk coverage
  • Production release cycles had to be extended to accommodate long manual regression test cycles
  • If defects were found, additional testing was conducted, but did not provide a proactive solution
  • End to end testing could not be completed due to time constraints

Accelerate 2017 is October 16-17 - learn more

LEARN MORE
X