A large telecommunications service provider in the Netherlands suffered from long test cycles and, as a result, from long delivery times for their core order management application due to limited access to external dependencies in the test environment. By introducing service virtualization they have been able to remove these access restrictions and successfully take their first steps towards Continuous Delivery.

1. Parasoft Proprietary and Confidential 1
2014-12-04
Towards Continuous Integration and
Continuous Delivery with Virtual Test
Environments
Bas Dijkstra

2. Parasoft Proprietary and Confidential 2Parasoft Proprietary and Confidential 2
Outline
 Introduction
 Service virtualization
 Case study
 The past – challenges
 The present – solutions
 The future – next steps

3. Parasoft Proprietary and Confidential 3Parasoft Proprietary and Confidential 3
About me
 Freelance test consultant
 The Future Group
 8+ years of experience
 Test automation
 Service virtualization
 Working together with Parasoft for 5 years

4. Parasoft Proprietary and Confidential 4Parasoft Proprietary and Confidential 4
What is service virtualization?
 Simulation of dependency behaviour

5. Parasoft Proprietary and Confidential 5Parasoft Proprietary and Confidential 5
Case study: the situation
 Large provider of triple play services over optic fiber
 Central order management system
 Test environment with many dependencies
 Around 10 systems for every order

6. Parasoft Proprietary and Confidential 6Parasoft Proprietary and Confidential 6
Case study: the past – challenges
 Order-specific data needs to be present in backend system
 Order configuration in backend requires manual intervention
 As a result:
 Limited test data
 Long test cycles
 Low test coverage
 No automated end-to-end testing

7. Parasoft Proprietary and Confidential 7Parasoft Proprietary and Confidential 7
Continuous delivery level

8. Parasoft Proprietary and Confidential 8Parasoft Proprietary and Confidential 8
Case study: the present – solutions
 Introduce Parasoft Virtualize for service virtualization
 Virtual backend behaves as if order data is present

9. Parasoft Proprietary and Confidential 9Parasoft Proprietary and Confidential 9
Case study: the present – results
 Fast provisioning of orders in test environment
 More control over test data, increase in test coverage
 Enabler for test automation
 Shift to Agile and Continuous Delivery
 Delivery every other week (instead of every three months)

10. Parasoft Proprietary and Confidential 10Parasoft Proprietary and Confidential 10
Shift left in the development process
 Developers use the virtual assets as well
 Allows for integration testing in development environment
 Bugs are found and solved before deployment to test
environment

11. Parasoft Proprietary and Confidential 11Parasoft Proprietary and Confidential 11
Automated smoke and regression tests
Deployment to
test environment
Automated smoke
test
Results sent
via email
Automated
regression test
Results stored
for later
analysis
Every weekend
and on demand

12. Parasoft Proprietary and Confidential 12Parasoft Proprietary and Confidential 12
Dynamic test environment configuration

13. Parasoft Proprietary and Confidential 13Parasoft Proprietary and Confidential 13
Full control over test data

14. Parasoft Proprietary and Confidential 14Parasoft Proprietary and Confidential 14
Continuous delivery level

15. Parasoft Proprietary and Confidential 15Parasoft Proprietary and Confidential 15
Case study: the future – next steps
 Improvements in continuous integration
 Automated deployment to acceptance environment
 Speed up delivery cycle even more
 Closer collaboration between development and operations

16. Parasoft Proprietary and Confidential 16Parasoft Proprietary and Confidential 16
Continuous delivery level

17. Parasoft Proprietary and Confidential 17Parasoft Proprietary and Confidential 17
Questions?
 bas.dijkstra@the-future-group.com (or find me on LinkedIn)
 www.parasoft.com