Proper way to use variable with slashes in RQM Execution Tool
I've got an RQM test script that requires a Windows-formatted network path as a parameter. My initial thought was this:
RQMExecutionTool.jar -variables=path:\\network\path\to\folder
This works somewhat, but I've found that my script doesn't understand situations where there a folder is called \\path\new\newfolder (due to the \n). So I try:
RQMExecutionTool.jar -variables="path:'\\network\path\to\folder'"
and this does not work. It causes a 500 error.
Then I try this:
RQMExecutionTool.jar -variables=path:\\\\network\\path\\to\\folder
This, too, does not work.
What's strange is that this DOES work:
RQMExecutionTool.jar -variables=path:\\folder
But this does NOT:
RQMExecutionTool.jar -variables=path:\\to\\folder
Does anyone have any idea of how I can approach this?
RQMExecutionTool.jar -variables=path:\\network\path\to\folder
This works somewhat, but I've found that my script doesn't understand situations where there a folder is called \\path\new\newfolder (due to the \n). So I try:
RQMExecutionTool.jar -variables="path:'\\network\path\to\folder'"
and this does not work. It causes a 500 error.
Then I try this:
RQMExecutionTool.jar -variables=path:\\\\network\\path\\to\\folder
This, too, does not work.
What's strange is that this DOES work:
RQMExecutionTool.jar -variables=path:\\folder
But this does NOT:
RQMExecutionTool.jar -variables=path:\\to\\folder
Does anyone have any idea of how I can approach this?
One answer
Use "/" instead of "\"
Comments
Thank you for the suggestion Subhajit. I'll try it, but I don't think it's going to work in this situation, as the target script is not a command-line script but it's going to an adapter from a 3rd party. If the 3rd party's windows only client can't or won't translate the "/" to "\", then this won't work.