Upload
bas-dijkstra
View
125
Download
2
Tags:
Embed Size (px)
Citation preview
Parasoft Proprietary and Confidential 1
2014-12-04
Towards Continuous Integration and Continuous Delivery with Virtual Test
Environments
Bas Dijkstra
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
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
Parasoft Proprietary and Confidential 4Parasoft Proprietary and Confidential 4
What is service virtualization?
Simulation of dependency behaviour
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
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
Parasoft Proprietary and Confidential 7Parasoft Proprietary and Confidential 7
Continuous delivery level
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
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)
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
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
Parasoft Proprietary and Confidential 12Parasoft Proprietary and Confidential 12
Dynamic test environment configuration
Parasoft Proprietary and Confidential 13Parasoft Proprietary and Confidential 13
Full control over test data
Parasoft Proprietary and Confidential 14Parasoft Proprietary and Confidential 14
Continuous delivery level
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
Parasoft Proprietary and Confidential 16Parasoft Proprietary and Confidential 16
Continuous delivery level
Parasoft Proprietary and Confidential 17Parasoft Proprietary and Confidential 17
Questions?
[email protected] (or find me on LinkedIn)
www.parasoft.com