Quantcast
Channel: Silk Test - Forum - Recent Threads
Viewing all articles
Browse latest Browse all 625

How to handle testing of different software releases (Different process/work directory path for each version)?

$
0
0

Hello all,

I've been running into an issue testing different releases of my company's software with Silktest Workbench (13.5) that I wanted to try and get some advice on.

There's an environment variable  on my machine that stores a partial path to the process that I want to test (i.e. WRK_HOME contains C:\Workspace\Home1.1, but the process is located in C:\Workspace\Home1.1\common\bin\process.exe). I want to use this variable because when the product is updated, the directory changes (i.e. from C:\Workspace\Home1.1 -> C:\Workspace\Home1.2), and the process is also stored in this directory, meaning that it will only run the release it was recorded in unless I manually change it. 

After looking at the documentation, I noticed that there were only a select number of environment variables that could be used in the process name/work directory, so I can't use WRK_HOME in the process name/work directory field of the visual test properties. Other than making a new database for each software release (i.e. one for 1.1, one for 1.2), is there a way for me to handle or replicate the usage of environment variables in Workbench?

If my explanation doesn't make sense, I can gladly reiterate. 

Thanks for the assistance!


Viewing all articles
Browse latest Browse all 625

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>