Service Virtualization

what is the best way to manage VSI between team members? 

Example, we have one virtual service which is created and connected in one of the test environment.. now we have many team members use the VSI as per their need and modify it.. how to effectively modify it.. unlike database , vsi is tough to get the updates from different teams each time before some one changes it.. 

Hello Jagath,

Have you had the chance to take a look at the Learning and Image Validation execution modes?

Here is the link to the documentation regarding the execution modes:

Execution Mode - DevTest Solutions - 10.1 - CA Technologies Documentation 

"learning mode automatically "heals" or corrects the virtual service to have the new or updated response from the live system."

Hope it helps.

Heloisa

Jagath,

How are the virtual services artifacts stored today? Are you using a source control of some sort where you store your entire DevTest project? It is highly recommended you use a source control to help keep track of changes and versioning of the artifacts. It is also important to draw the line of when to separate virtual services so that each team or individual has a copy that contains transactions related to his/her test cases. Because if everyone keeps enhancing the same virtual service image with their own transactions then the virtual service image will become very hard to maintain in the future. So my advice would be to use source control and to isolate relevant test case scenarios in separate virtual service images.