SoapUI Settings.XML file is not overridden in LoadUI
I am Using SoapUI 3.6.1 and LoadUI 1.5
In my scenario I have a 3 layered property set up:
The endpoint url is http://${#TestSuite#HostPort}/sample.asmx
Inside the TestSuite Properties HostPort = {#Global#DEV}
Inside the Global Properties DEV = 192.168.xxx.xxx
Running in SoapUI this works, running in LoadUI with out changing the file the tests also pass. Now I am testing to make sure when I change the settings.xml file location I control those global properties to know which environment I am sending request to:
1) Closed both SoapUI and LoadUI
2) I coped the existing "soapui-setings.xml" file over to a new location
3) Changed the "DEV" to point to 000.000.000.000 (should obviously fail if we call that IP)
4) Opened LoadUI pointed the SoapUI runner to a the copied settings.xml file.
5) Closed LoadUI and reopened LoadUI (seems like you need to do this to reload the file?)
6) Ran the LoadUI project.
The problem is the test still passes which means it is not grabbing the updated file. To make sure I knew which file the SoapUI runner is accessing I then:
7) Changed the new file back to tthe correct IP address so that the test would pass.
8) Change the original file (C:\Documents and Settings\User\soapui-setting.xml) to 000.000.000.000
9) Reopened LoadUI
9) Run the LoadUI Project with the SoapUI runner settings still pointing to my new location on my D drive.
It now fails becuase it is still accessing the original XML file.
I understand that we can override the TestCase Properties, but I would prefer to point to one file and update the file if I need a change vs updating every SoapUI runner if I want to point to a different environment; which is what I thought changing the settings.xml file would do? I plan on having many soapUI test cases run (50-60) and want to make one change that will effect them all.
Is this a bug? If not what does overriding the setting file do?
Does anyone have any ideas?
In my scenario I have a 3 layered property set up:
The endpoint url is http://${#TestSuite#HostPort}/sample.asmx
Inside the TestSuite Properties HostPort = {#Global#DEV}
Inside the Global Properties DEV = 192.168.xxx.xxx
Running in SoapUI this works, running in LoadUI with out changing the file the tests also pass. Now I am testing to make sure when I change the settings.xml file location I control those global properties to know which environment I am sending request to:
1) Closed both SoapUI and LoadUI
2) I coped the existing "soapui-setings.xml" file over to a new location
3) Changed the "DEV" to point to 000.000.000.000 (should obviously fail if we call that IP)
4) Opened LoadUI pointed the SoapUI runner to a the copied settings.xml file.
5) Closed LoadUI and reopened LoadUI (seems like you need to do this to reload the file?)
6) Ran the LoadUI project.
The problem is the test still passes which means it is not grabbing the updated file. To make sure I knew which file the SoapUI runner is accessing I then:
7) Changed the new file back to tthe correct IP address so that the test would pass.
8) Change the original file (C:\Documents and Settings\User\soapui-setting.xml) to 000.000.000.000
9) Reopened LoadUI
9) Run the LoadUI Project with the SoapUI runner settings still pointing to my new location on my D drive.
It now fails becuase it is still accessing the original XML file.
I understand that we can override the TestCase Properties, but I would prefer to point to one file and update the file if I need a change vs updating every SoapUI runner if I want to point to a different environment; which is what I thought changing the settings.xml file would do? I plan on having many soapUI test cases run (50-60) and want to make one change that will effect them all.
Is this a bug? If not what does overriding the setting file do?
Does anyone have any ideas?
