Process deadlocks are endemic to parallel and Agile development environments, where different teams are simultaneously working on interconnected system components—and each team needs to access the others' components in order to complete its own tasks. But when a team ends up waiting for access to dependencies, agility is stifled. One way to break free of these constraints is to use service virtualization to simulate interactions between the application under test and the dependencies that are unavailable or difficult-to-access for dev/test purposes. This presentation explains how service virtualization can help you eliminate the delays created by unavailable and evolving dependencies so you can save time, money, and effort. It will also share case studies that show specific cases where service virtualization helped organizations compress their testing cycles to keep pace with the demands of Agile development.
5. 55
Lack of Trustworthy Access
The average number of
dependent application
associated with the
System Under Test (SUT)
30
BUT, Dev/QA only have
“trustworthy” access to
6
of the applications
6. 66
Survey Results…
When testing with a
dependent application
only need access to a
small percentage
of the applications
functionality
20%
9. 99
What is Service Virtualization?
Service Virtualization delivers a
simulated dev / test environment
allowing an organization to test
anytime or anywhere
11. 1111
How it works?
1 Capture
Virtualize Server
Traffic Logs
Application Under Test
3 Model
Parasoft Virtualize
4 Test
12. 1212
What can be virtualized?
Source: voke Market SnapshotTM Report: Service Virtualization – December 2012
4%
22%
34%
37%
53%
56%
65%
0% 10% 20% 30% 40% 50% 60% 70%
Other
Architecture
Partner software
Mainframe
Third-party applications
Third-party services
Applications
13. 1313
Rationale for SV adoption
Source: voke Market SnapshotTM Report: Service Virtualization – December 2012
7%
33%
59%
62%
72%
0% 20% 40% 60% 80%
Other
More realistic performance
testing
Parallel development
Scheduling constraints
Restricted access to dependent
services, components or systems
14. 1414
Use Case: Reducing Testing Time
Testing time is reduced by 27 days when using Parasoft Virtualize.
Database Mainframe Application Web Service 3rd Party
Developer QA & Test Performance
Test Engineer
Developer QA & Test Performance
Test Engineer
15. 1515
Use Case: Reducing Costs
The customer saved $ 840 000 and 14 days (83%) of configuration time.
Requested 7 x Test Environments
11 x back-end systems
Zoomed one of test Environments
Service Virtualization Server
7 x Virtual Test Environments
16. 1616
Use Case: Reducing Waiting Time
Waiting time for QA team reduced by 61 %.
QA & Test QA & Test
17. 1717
Use Case: Reducing Access Fees
Parasoft Virtualize saved $ 560 000 of access fees.
Mainframe Mainframe for tests Mainframe for testsMainframe
18. 1818
SV ROI by VOKE
Source: voke Market SnapshotTM Report: Service Virtualization – December 2012
Service Virtualization ROI Changes %
Greater Availability of Services over 50%
Decreased Software Cycles 25% - 50%
Increased Test Coverage 50% - 90%
Shorter Test Cycle Times 58%
Faster Time to Market 10% - 50%
Fewer Production Defects 5% - 75%
19. 1919
ROI of Service Virtualization
Accomplishing Schedule
Raising Quality
Reducing Costs
20. 2222
Awards
July 24th, 2012 - Parasoft Virtualize
won Jolt Award in the category of
Utilities.
February 14th, 2013 - Info-Tech Research Group
awarded Parasoft with Software Testing Trend
Setter in the category of
Software Testing Market Innovator.