In ReadyAPI 2.6.0, JDBCconnectionString are not updated when env changes using setActiveEnvironment
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In ReadyAPI 2.6.0, JDBCconnectionString are not updated when env changes using setActiveEnvironment
We recently upgraded the ReadyAPI project from v2.3.0 to c2.6.0. After upgrage we noticed that the connectionString in JDBC requests are getting hardcoded and not getting updated when the environment is changed via setActiveEnvironment from Java code.
In v2.3.0, connections string where saved as
<con:connectionString>${#Project#ConnectionString}</con:connectionString>
whereas in v2.6.0 its set as
<con:connectionString>jdbc:db2://<host>:<port>/<user>:user=${dev.DBUser};password=${dev.DBPassword};</con:connectionString>
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @NewAutoTester,
It sounds like an issue in ReadyAPI 2.6 to me. I recommend that you consult with our Support Team about this behavior. Could you please contact them and let us know the results?
http://support.smartbear.com/message/?prod=ReadyAPI
Thanks in advance.
Tanya Yatskovskaya
SmartBear Community and Education Manager
