ContributionsMost RecentMost LikesSolutionsRe: Integration tab shows "Browser Component is disabled" This issue has returned from one to another day in ReadyAPI 3.30.0😫 Re: Unable to send soap request when connected to Corporate VPN Did you try to browse to the WSDL with your (default) webbrowser? It should show the WSDL file, when you're authenticated correctly... if not, then this is probably the issue. Re: Integration tab shows "Browser Component is disabled" Nope... after update 3.10.1 still not solved (in ReadyAPI). Hopefully next update. Re: Integration tab shows "Browser Component is disabled" We're having the same issue with the latest ReadyAPI version (3.10.0), but also older versions like 3.5.1. Support ticket has been made: 00493046 Thanks for contacting the SmartBear support team.I can reproduce the issue with ReadyAPI 3.10.0 and our test Bitbucket Cloud account, as well. A bugRIA-18398 has been created for that.I will let you know when I have any updates from our developers regarding the matter. Sorry for the inconvenience.Regards, Julia Kolosova Customer Care Engineer Re: Variable keystore for each single teststep, based on environment Confirmed: After upgrading to ReadyAPI 3.1 the problem is solved: »The SSL Keystore field is a dropdown & textarea »I'm able to 'write' (variablies) in the SSL Keystore field for each teststep »The SSL keystore is reading values from olderReadyAPI versions (ie ReadyAPI 2.5) Re: SSL Key fields in all teststeps are lost when upgrading from 2.5 to 2.6 and higher. Confirmed: After upgrading to ReadyAPI 3.1 the problem is solved: »The SSL Keystore field is a dropdown & textarea »I'm able to 'write' (variablies) in the SSL Keystore field for each teststep »The SSL keystore is reading values from olderReadyAPI versions (ie ReadyAPI 2.5) Re: how to create config file can call in test (keyword) ReadyAPI works with so called 'Environments'. Assuming you work with SoapUI; just go to the 'Environments'-panel where you can define all environments (i.e UAT, Test, Production) including the user-credentials. This will make it ease to switch from environments without changing URL's and the user-credentials for each teststep. Re: Set SSL Keystore using Groovy on Test Step level The use of variable keystores in "custom" properties was broken since ReadyApi 2.5. Today I received a message from Smartbear's dev-team that they've fixed it in their upcoming release (planned in February 2020). More info: https://community.smartbear.com/t5/SoapUI-Pro/Variable-keystore-for-each-single-teststep-based-on-environment/m-p/196259/highlight/true#M44874 Re: Allow SoapUI assertions to vary depending on selected environment Say you have a TST-environment where input A will give back output B (and you assert output B). Say you also have a UAT-environment where input A will give back output C. When you switch to UAT and you will send input A, then the assertion willfail because it was expecting output B but actual value was C. It would be nice if assertions could also be variable, based on the selected environment. I can imagine that UAT-environment has more production-like data, compared to a TST-environment. Is this what you want Minophis? Re: Variable keystore for each single teststep, based on environment Dear sonya_myou made my day!