Testing remains a bottleneck for development teams, or, worse, a luxury. Just ask Frank Jennings, TQM performance director for Comcast. Like many test professionals these days, he faces many scenarios for exercising a diverse array of consumer and internal products and systems.
“The real pain point for my team was staging-environment downtime,” he said in an October 2012 webinar moderated by SD Times editor-in-chief David Rubinstein. “Often, downstream systems were not available, or other people accessing those dependent systems affected test results.”
Automating the test portion of the life cycle is often an afterthought, however. “People are looking for operational efficiency around the concepts of continuous release. We walk into companies that say ‘We want to go to continuous release,’ and we ask, ‘What are your biggest barriers?’ It’s testing,” said Wayne Ariola, chief strategy officer for Parasoft, a code quality tool vendor.
“Today, I would say 90% of our industry uses a time-boxed approach to testing, which means that the release deadline doesn’t change, and any testing happens between code complete and deadline. That introduces a significant amount of risk. The benefit of service virtualization is you can get a lot more time to more completely exercise the application and fire chaos at it.”
Related Search Term(s): service virtualization
Share this link: http://sdt.bz/67589