davinci020
Occasional Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: SSL Keystore Request Property not working since 3.6.2
I'm having exact the same problem and downgraded back to version 3.61.0. Already made a ticket at the servicedesk like weeks ago, but still no solution. Ticket eventually got closed because I couldn't send them my reproduction-video (because file was too large for email). Meanwhile 3.63.0 still same problem occurs and my whole team is stuck with 3.61.0.40Views0likes0CommentsRe: 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 bug RIA-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 Engineer2.6KViews1like6CommentsRe: 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 older ReadyAPI versions (ie ReadyAPI 2.5)2.5KViews1like0CommentsRe: 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 older ReadyAPI versions (ie ReadyAPI 2.5)1.4KViews0likes0CommentsRe: 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.2.3KViews0likes0CommentsRe: 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#M448744.9KViews0likes3CommentsRe: 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 will fail 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 ?1.6KViews0likes0Comments