I've had the same issue. My solution is not perfect, but workable. For every testsuite, I've added a testcase that just does the configuration.
So I have a few property steps, containing the connect strings.
Then a few property transfers that transfer the connect strings into a project/testsuite variable. I make sure the last one is the one I want to test on currently.
For the JDBC-steps the connection string is read from the project/testsuite variable.
Would this work for you?
Hey Jack,
That seems like a reasonable solution to get around it for now. Would you be able to provide me with an example of how you've set it up so i can give it a go please?
I've attached a screenshot so you can get an idea of how my workflow looks.
So I've got a couple of instances of Properties 'database', and Property transfer 'database'. The properties step contains the web service, database connect string and some specific values I need.
The transfer puts these in project variables.
In the SOAP-steps I use ${#Project#Endpoint} as endpoint. In JDBC-steps I use #Project#dbConnectString as connection string.
Does this clarify things?
