More Parameter P(a)rob(a)lems!
All, I'm a bit baffled here, as I'm sure this was working for me the other day! I have a script function that takes 5 string params - 4 of which are optional, so a call might look like: ...
Forum Discussion
Hi Tanya,
Calling the function with multiple parameters isn't the problem - it's if any of them are undefined...
Eg if I supply a value for the 2nd parameter of "myteststring" - then TC recognises it as a String variable, and "myteststring" gets entered into our AUT. However, if I then leave delete "myteststring" from the definition of the 2nd parameter, TC reverts it to a Variant - and when I run the test, TC enters "UNDEFINED" into the AUT!
I've found a workaround where in each function I can do "paramname = aqConvert.VarToStr(paramname)" .... but this isn't ideal!
I've no objection to sending a zip of our test project, but I would guess that for NDA type reasons my employers would not want me posting it on a public forum... I believe we are in the process of renewing our support license - maybe I should chase that and raise a support call, referencing this thread?
Calling the function with multiple parameters isn't the problem - it's if any of them are undefined...
Eg if I supply a value for the 2nd parameter of "myteststring" - then TC recognises it as a String variable, and "myteststring" gets entered into our AUT. However, if I then leave delete "myteststring" from the definition of the 2nd parameter, TC reverts it to a Variant - and when I run the test, TC enters "UNDEFINED" into the AUT!
I've found a workaround where in each function I can do "paramname = aqConvert.VarToStr(paramname)" .... but this isn't ideal!
I've no objection to sending a zip of our test project, but I would guess that for NDA type reasons my employers would not want me posting it on a public forum... I believe we are in the process of renewing our support license - maybe I should chase that and raise a support call, referencing this thread?