Forum Discussion

davinci020's avatar
davinci020
Occasional Contributor
6 years ago

Variable keystore for each single teststep, based on environment

Dear Smartbear friends! This is my very first post on the community site :smileylol: #NoobAlert My situation I have a webservice with 3 environments (integration, acceptation & production)...
Automation Environments
SOAP
SSL Keystore
  • davinci020's avatar
    davinci020
    5 years ago

    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)

TanyaYatskovska's avatar
TanyaYatskovska
SmartBear Alumni (Retired)

Hi davinci020,

 

Welcome to the SmartBear Community :)

 

Did you find the answer to your question in the topic, HimanshuTayal suggested?

Please let us know if you need any more assistance.

davinci020's avatar
davinci020
Occasional Contributor
6 years ago

Hi there TanyaYatskovska

I didn't manage to figure out how to fix this problem according to the documentation (due to Easter holiday),

but I will get back at it soon and hopefully accept the solution and give kudo's to HimanshuTayal.

 

...to be continued

  • davinci020's avatar
    davinci020
    Occasional Contributor
    6 years ago

    Dear TanyaYatskovska and HimanshuTayal unfortunately the solution didn't fit my needs. Because this would change the certificates at global, project, testsuite and testcase level. For me there's no reason to change this with a groove script, because I can navigate to the properties/settings.

     

    The problem is that I have 2 or 3 actors in each testcase, and both actors have different certificates for every environment. So when I swich to another environment, all teststeps should remain the same but then I use other users, passwords and certificates in the teststep-properties. (Our certificates for test-environment are not valid on acceptance-environments, neither are users and passwords).

     

    I don't understand why Smartbear decided to only allow dropdown fields as SSL Keystore in every request, since 2.6.

     

    If I could use ${#Project#CertificateUserA} in each teststep, then I could specify the certificate.p12 for each environment in the project-properties :(