ContributionsMost RecentMost LikesSolutionsRe: Is there a way to store a global or project property inside a virtualized service response script? I am running it the software locally and trying to hit the deployed virtualized service. It will run headless in the future in a Jenkins pipeline, but we were running into errors before that. Re: Is there a way to store a global or project property inside a virtualized service response script? Thank you. That worked perfectly. Would you happen to have any idea why that script would fail when it is running on the cloud? Re: Is there a way to store a global or project property inside a virtualized service response script? I need to write the data from the virtual service to the test step. Thanks for the help. Re: Is there a way to store a global or project property inside a virtualized service response script? I can't write it to the test step because as far as I know you don't have access to the testRunner object inside of scripts that are written inside of a virtual API. Is there a way to store a global or project property inside a virtualized service response script? I have a virtualized service that is running a script for it's response. Is there a way that I can store properties in that script so that they would be accessible inside groovy scripts inside the testing portion of the project instead of the virtualization portion? The issue I was running into was that testRunner is not accessible there. Normally that is what I would use to save properties. Solved