Updated to new wsdl on a new server but test steps are linked to database on previous server
Hello,
I have been using ReadyAPI to test some SOAP services. I updated my project definition to a new wsdl which is on a different server/environment now, but the test steps are still linked to the database of the previous server/environment. To be more specific:
1. Had a project, test case and test steps (lost of scenarios) using a wsdl definition on the dev environment which writes to a database on the dev environment as well.
2. Have been provided with a new wsdl definition for the QA environment - supposedly everything has been deployed to this new environment: the services, the database, etc.
3. Updated the definition for my project providing the new wsdl (have confirmed that it was successful and my project displays now the QA wsdl definition)
4. When I run my old test steps (scenarios) that write to the database, they keep using the database on the dev environment instead of the QA database.
It looks like everything is still linked to a database a should not use anymore. I shouldn't need to re-recreate all my test steps, they should be re-usable and point now to the QA database.
So, other than "Update Definition" and provide the new wsdl, what else I am missing?
Please any ideas?
Thanks,
Joel
ok... the problem was that, even when I updated the definition to use the new URL and I selected 'yes' to the question about updating the end point for the service requests as well, still the test steps (for tons of scenarios I have for the basic service requests) had the end points with the old URL.
Why does ReadyAPI do not update the end points for the test steps as well? - I believe this should by guaranteed.
Anyways, the link below helped me to find the answer and I am already in the process of parameterizing the URL, then I have to change the end point for each test step to use the value of the parameter.
https://community.smartbear.com/t5/SoapUI-Open-Source/How-to-change-the-end-point/td-p/24545
