Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Deploy and Destroy Complete Test Environments

7,288 views

Published on

Slides from my talk on service virtualization, containers and cloud at TestCon 2016 in Vilnius, Lithuania

Published in: Software
  • Be the first to comment

  • Be the first to like this

Deploy and Destroy Complete Test Environments

  1. 1. Deploy and Destroy Complete Test Environments Service Virtualization, Containers and Cloud Bas Dijkstra bas@ontestautomation.com www.ontestautomation.com @_basdijkstra
  2. 2. Continuous Delivery Release Build Test Deploy
  3. 3. Continuous Testing Release Build Test Deploy
  4. 4. Test environment impediments System under test Mainframe SaaS dependency Backend system Mobile app No suitable test data Limited access Under development Access fees
  5. 5. The T-shaped tester: What about the T-shaped test environment? Under control 100% availability Scalable Realistic performance Suitable test data
  6. 6. Service virtualization System under test Virtualized mainframe Virtualized SaaS dependency Virtualized backend system Virtualized mobile app Unrestricted access Unrestricted access Unrestricted access Unrestricted access
  7. 7. Service virtualization _Simulation of dependency behavior _Oblivious to dependency implementation _Virtual assets
  8. 8. Virtual asset creation _Record and playback _Based on specifications
  9. 9. Implementation considerations _Start small _Model just enough _Learn and expand
  10. 10. Testing process benefits _Test earlier _Test more often _Test more
  11. 11. Taking service virtualization to the next level _Continuous Delivery integration _Containerization _Cloud
  12. 12. Test environments on demand _Recreate exact same initial situation every time _Always available _Scalable
  13. 13. Test environments on demand Build server commit Provision virtual test environment Deploy application under test Run tests
  14. 14. Server hardware Host operating system Docker engine Bins / libs Bins / libs App CApp BApp A
  15. 15. Example: Hoverfly (SpectoLabs) _HTTP(S) only _Light-weight and open source _http://hoverfly.io
  16. 16. Example: Parasoft Virtualize _Support for many message types and protocols _Commercially licensed _Environment Manager _http://www.parasoft.com/virtualize
  17. 17. Virtualize + VSTS + Azure commit Parasoft Environment Manager Simulated test environment Application under test AUT Parasoft SV Azure cloud VM Host OS Server On-demand test environment in the cloud
  18. 18. Organizational decisions $ $$$ $$ $ $ $ $ $ $ $ $ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
  19. 19. Infrastructure OR On premise In the cloud
  20. 20. Knowledge OR Inside development teams Center of Excellence
  21. 21. Development OR In-house Outsourced
  22. 22. Example SV maturity journey
  23. 23. Case study: education Infrastructure Knowledge Development
  24. 24. Case study: financial services Infrastructure Knowledge Development
  25. 25. _ Email: bas@ontestautomation.com _ Blog: http://www.ontestautomation.com _ LinkedIn: https://www.linkedin.com/in/basdijkstra _ Twitter: @_basdijkstra

×