Forum Discussion
SmartBear_Suppo
11 years agoSmartBear Alumni (Retired)
Hi,
As I understand you keep your wsdl locally on file system. And in composite project or even simple project it keeps reference of wsdl file with an absolute path, which is unfortunately machine dependent. So, if you import test suites created in another machine you will face this problem.
One workaround can be to have the WSDL interface settings file local and not in Git. Since settings.xml file keeps the reference of wsdl file so there you can just change the wsdl file path to the one you have on your system. Here is there directory structure of WSDL interface.
<folder for each WSDL Interface>
settings.xml – Interface specific settings
<xml file for each operation> - contains all settings and requests for the operation
Hope this helps little bit.
Regards,
Shadid
SmartBear Sweden
As I understand you keep your wsdl locally on file system. And in composite project or even simple project it keeps reference of wsdl file with an absolute path, which is unfortunately machine dependent. So, if you import test suites created in another machine you will face this problem.
One workaround can be to have the WSDL interface settings file local and not in Git. Since settings.xml file keeps the reference of wsdl file so there you can just change the wsdl file path to the one you have on your system. Here is there directory structure of WSDL interface.
<folder for each WSDL Interface>
settings.xml – Interface specific settings
<xml file for each operation> - contains all settings and requests for the operation
Hope this helps little bit.
Regards,
Shadid
SmartBear Sweden
Related Content
- 2 years ago
- 5 years ago