cancel
Showing results for 
Search instead for 
Did you mean: 

Variable keystore for each single teststep, based on environment

SOLVED
Highlighted
Occasional Contributor

Variable keystore for each single teststep, based on environment

Dear Smartbear friends!

This is my very first post on the community site Smiley LOL

#NoobAlert


My situation

I have a webservice with 3 environments (integration, acceptation & production).

For each seperate teststep-properties I use variables like;

username: ${#Project#Username}

password: ${#Project#Password}

ssl keystore: ${#Project#Certificate}

 

The benefit is that I can manage these credentials in the Project Custom Properties.

So when I switch from environment, I only have to change 1 Project Custom Properties and all seperate teststeps will obey the Project Custom Properties. If I want to switch user or certificate, I can do that on the single Project Custom Properties as well.

 

But nowwww....

The problem

Since I've upgraded to ReadyAPI 2.6.0 I've lost ${#Project#Certificate} in the ssl key store field from all seperate teststeps and there's no way to write this back, because this field suddenly became a dropdown-list.

 

SSL Keystore.png

Can anyone give me tips how to fix this properly?

Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Occasional Contributor

Re: Known Issue: 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)

View solution in original post

12 REPLIES 12
Highlighted
Community Leader

Re: Variable keystore for each single teststep, based on environment

Hi @davinci020 ,

 

Please refer below documenation. Hope it will solve your problem:

 

https://www.soapui.org/scripting-properties/tips-tricks.html

 

Go to Section: 1.2 Get and Set SoapUI Preferences

 


Click "Accept as Solution" if my answer has helped,
Remember to give "Kudos" 🙂 ↓↓↓↓↓



Thanks and Regards,
Himanshu Tayal
Highlighted
Community Manager

Re: Variable keystore for each single teststep, based on environment

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.

---------
Tanya Gorbunova
SmartBear Community Manager

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today
Highlighted
Occasional Contributor

Re: Variable keystore for each single teststep, based on environment

Hi there @TanyaGorbunova

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

Highlighted
Occasional Contributor

Re: Variable keystore for each single teststep, based on environment

Dear @TanyaGorbunova 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 😞

Highlighted
Occasional Contributor

Known Issue: Variable keystore for each single teststep, based on environment

This issue is a defect we have in ReadyAPI 2.6.0 and 2.7.0.

The defect id is RIA-10019.

Highlighted
Community Manager

Re: Known Issue: Variable keystore for each single teststep, based on environment

Thanks for the update, @davinci020!

I hope the issue will be fixed very soon.

---------
Tanya Gorbunova
SmartBear Community Manager

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today
Highlighted
Established Member

Re: Known Issue: Variable keystore for each single teststep, based on environment

Hi,

 

I have exactly the same problem here.

 

I've been looking for the roadmap of ReadyAPI or SoapUI but I couldn't find it. Could you tell me when it's planned to release the fix for this?

 

Thanks

 

 

Highlighted
Occasional Contributor

Re: Known Issue: Variable keystore for each single teststep, based on environment

Hi @isabel1 the support-team didn't gave me idication when they'll fix it, but they will notify me when they do.

Best solution for now is to go back to ReadyApi 2.5.

Occasional Contributor

Re: Known Issue: Variable keystore for each single teststep, based on environment

Unfortunately it's not fixed in ReadyApi 3.0.0.

Our whole test-department is waiting since version 2.5.0 and we can't upgrade to the latest version ever since.

Smiley Sad

 

New Here?
Join us and watch the welcome video:
Announcements
TechCorner Leaderboard
Want a fun and easy way to learn ReadyAPI and show off your skills? Try solving weekly TechCorner challenges and get into the Leaderboard!


Challenge Status

Compare an expected JSON value and actual response in Events

Participate!

Fetch value/data from JSON response using Groovy Script

See replies!

Filtering data retrieved from a DataSource

See replies!

Get data from Petstore and add it to Excel sheets

Participate!
Top Kudoed Authors