Generally app version and change management is done outside the realm of Service Virtualization. I have seen customers use SVN, TFS, Git, etc to store and version VS. However your ask of integration testing, reducing cost of test environments, etc are primary use cases of SV. Anytime you want to do Functional Testing, Performance Testing, Integration Testing or Unit Testing, SV is a master at those requirements and helps to save a lot of time, effort, $$ thereby enabling a huge ROI.
------------------------------
Head of Service Virtualization Product Management
CA Technologies - A Broadcom Company
------------------------------
Original Message:
Sent: 04-24-2020 03:00 AM
From: Anil Kumar
Subject: SV's ability with application versioning and change management for integration strategy
Hi all,
Hope all are safe and home.
We need to understand how SV can help w.r.t manage application versioning and change management in order to have an integration strategy which by:
- streamlines application integration (through the whole application lifecycle)
- streamlines integration tests and define clear boundaries for those
- reduces the cost of test environment
- increase the scalability of test environment
- decouples the various application integration wherever possible
Also , by performing SV PoC we need to address :
- What does the integration strategy should look like in the landscape
- What are the gaps in terms of process, practices, change in technology, prerequisite to move from our current state to the target state which will enable the integration strategy
- What are example of change management and change release process to support the strategy
Kindly provide your inputs in this regard. Any pointers / links to doc / previous use case / poc experience would definitely help.
Thanks
Anil