Hi,
Firstly, for transparency, ChrisAdams is my home account and ChrisA is the account I use at work. Licensed SoapUI user at work etc.etc.
Anyhow, the way I described it, albeit badly, does work. Might not be what you want, but I'll try and step it out anyway. If I have misunderstood, what you're trying to achieve, then say.
In the Environments editor, you can define service URLs and JDBC Connections for each environment. E.g. Test, Pre-Prod and Prod. Each JDBC connection is 'named'. E.g. CUSTOMERDB. For that you define the driver and connection details.
When you create a JDBC Test Step, you select the 'named' connection of interest. The other fields, e.g. Driver and Connection, are then populated from the settings in the Environments editor.
If you switch enviornments, the details in the JDBC test step are updated to point at. the right db for the enviroment.
Conversely, if you update the named JDBC connection to use a new driver and conn details, then this is propagated down to each JDBC Test Step using that connection. I have tested this, but I cannot share any screenshots. Nor can I do this from home as I don't have the Pro licensed version.
Maybe richie could do some screenshots.
This link SoapUI Environments , shows the Environment editor and this link JDBC Connections shows the JDBC Editor. The Name column indicates what I mean by 'named' connections.
For each JDBC Test Step (link ), the Connection details are tethered back and forth with JDBC Connections. In the step, if you change the connection, then the greyed-out Driver, Conn String and Password are update. Same thing happens if you update the named connection in the Environments editor, even a driver change works.
