I have unbelievable problem with @community_admin0 again which drives me crazy… I’m using data driven testing with binding variables from Excel on test suite level. So far I’ve used a lot of sources and mapped more than 300 variables on different test cases.
Now when I’m on 98% of my POC and after I’ve downloaded latest version of @community_admin0 variable binding is not working as expected anymore!
I’m trying to bind variables on test suite level and only half of them get bindings and half doesn’t without any information, error or reason why!
Blue marks a variable that is mapped successfully, and red marks a variable that is not.
Notice that in the case of variable description, it has a newline character, when Katalon read its value, the value will be “description\n”, which will not map to column with name “description” in your Test Data. This also applies for other mapped and unmapped variables.
Please try to delete the new line characters ( you could perhaps use an online XML formatter). Could you also verify that on your colleague’s machine to see if it’s any different, and also on the previously working version.
@ThanhTo Thank you for you effort. I’m copying variables sometimes using script mode.
Issue probably happen during copy/paste from one test case to another or from Katalon to Notepad++ and back to Katalon.
If you wonder why I’m copy/pasting code from Katalon to Notepad++ and back that’s because of another issue with Katalon removing parens when moving from script view to manual view after a change in manual view, this is still not fixed in latest version even though release notes state it is:
The error you said was about the Script mode of a test case, but the variables are in a separate Script tab. Could you elaborate more, since I am failing to see the connection between the paren problem with the variables.
@ThanhTo The connection is I have to use external text editor because of another issue with parens. So in other words if I wasn’t forced to use external editor I would never bumped into issue with ‘\n’ character in variables
I can confirm removing ‘\n’ character in variables script mode resolved issues with variables, they are mapped now.