String params not treated as regex's...

Hi Steve.



I think you won't face problems with passing backslahed strings into your functions from KDTs.



I played passing KDT variable, KDT parameter and constant into JScript function: variable and KDT parameter came thru without any modifications. As for constant parameter, TC replaces single backslashes with double ones (and backwards) automatically. Just tell your less techy colleagues not to modify parameters directly in parameter string but double click on parameters section and edit them in Operation Parameters dialog.



I think the best solution for you is in using KDT/Project/Suite variables for your path definitions.



I wrote function which posts parameter passed into TC log:

function getFileName( pPathAndFile )

{

  Log.Message( pPathAndFile );

  return;

}

 

This function was called from KDT passing constant, KDT parameter and KDT variable.

See attached screenshots.