ContributionsMost RecentMost LikesSolutionsRe: Unable to disable properties step Makes sense, thank you Re: Unable to disable properties step nmrao Looks like a viable option even though i wanted to have everything consolidated inside the project to make it easier to export and share. Unfortunatelly until the disable option of the properties step does what is inteded or an environments functionality is added to SopaUI, this is the only option that is maintanable. Thank you Re: Unable to disable properties step Hi all Thank you very much for your feedback. Unfortunatelly nulling the values is not an option since i want to keep the actual value. What i am trying to do is something like the environments functionality there is in postman, where we can have multiple sets of variables but with different values and at each run choose which set to use. Currently we are not interested in automatically switching from one set to another, manual switching before the run is just fine. The only solution i have found till now is to change the order of the properties step before running the test case. Thank you Re: Unable to disable properties step Hi No i just want to run the test for one value e.g. non-fiction. Basically i want to have multiple sets of credentials for the same API because i need to run the tests with a different set every time. Instead of replacing the values of the properties i just want to disable all the property steps that i am not interested in and leave only one that contains the credentials i want to use. Re: Unable to disable properties step Hi again. Attached you can find a sample of the actual test i am trying to implement. I have two poperties steps "properties" and "properties alternative" with the same property but with different value. Even if the second in order property step is disabled the value used when the request is run is the one from the second step. I just noticed that if i change the order of the properties step everything works as expected. So for me the error here is that even though the properties step is disabled soap ui runs it and sets the values. Re: Unable to disable properties step Sorry for that i have attached the images. I am trying to create a test case with two properties steps. Both property steps will contain the same properties but with different values. I want each time i run the test to have one of the two property steps enabled and use the values in there. Having two property steps and alternating them when needed will permit me to have the same test steps but different values for the properties in each run. If there is an alternative that you think it might work please feel free to suggest. Thank you Re: Unable to disable properties step Bellow you can find the request with the properties step enabled and with properties step disabled. No i haven't tried it in any older version. Thank you Enabled Disabled Re: Unable to disable properties step I have tried deleting and recreating the properties step as well as starting a new project from scratch. The behaviour is always the same. My expectation would be that by disabling the properties step should be enough to make the depending steps fail but unfortunatelly this is not happening. I am using Thank you for your help Unable to disable properties step Hello I have created a test suite with a test case where i have included a properties step along with a rest request that depends on the properties set in the properties step. The first time i run the test case the property is correctly set and all the steps in the test case succeed. If i now disable the properties step, the test case still succeeds because for some reasons the properties are still set even though i have disabled the properties step. If i now change the property in the disabled properties step, the rest of the steps will be executed with the new value even if the property step is still disabled. Is this a bug or a missing something. Thank you Solved