## Operating System: Windows 10
## Katalon Studio Version: <= 5.8.6
## Katalon Studio logs: not relevant
**## Environment (for Web testing): **not relevant
**## Environment (for Mobile testing): **not relevant
## Steps to reproduce
Normally, the Groovy language standard supports multiline strings by using tripple single quotes (see here) and triple double quotes (see here). Therefore I like to use this technique to formulate my database queries in the code for test cases clearly, like this:
def sqLiteString1 = sqLite.execute(new String('''
UPDATE myTable
SET
foo = null;
'''))def String $table = 'myTable'
def sqLiteString2 = sqLite.execute(new String("""
DELETE FROM $table
WHERE
foo = false;
"""))
I know I should try to make the complexity of the Test Cases more lean and instead outsource such code to Custom Keywords methods. But at the beginning of a new development I still work very exploratively and don’t want to deal with the certainly very important questions of code abstraction yet, which is why I edit all new code parts within one script.
## Expected Behavior
Even after I switched to the manual view to further edit the test case there (e.g. I add a new test step), the above code should still be accepted and processed by Katalon Studio as it stands, since it conforms to the Groovy language standard.
## Actual Behavior
But when I return to the script view afterwards, my above multiline strings are incorrectly corrected as follows:
def sqLiteString1 = sqLite.execute(new String('\n\tUPDATE myTable\n\t\tSET\n\t\t\tfoo = null;\n'))
def String $table = 'myTable'
def sqLiteString2 = sqLite.execute(new String("
DELETE FROM $table
WHERE
foo = false;
"))
That is, the text content between the tripple single quotes has been converted to a single line, marked by single single quotes. And in the other case the triple double quotes were also converted to single double quotes, but the line breaks remained, which of course leads to script errors, which I have to correct manually in the code afterwards.
Both are not viable solutions. I suspect it won’t be easy to translate such multi-line strings into the manual view (and back again), but it certainly isn’t impossible, is it?
Please find a way, these multiline strings are simply too useful for me to do without them. Many thanks in advance!
**## Screenshots / Videos: **unnecessary
As far as I know, you don’t use the Manual View at all and that’s probably the only reason why you haven’t encountered this problem yet, isn’t it? It really only occurs after you have made changes to the test case in the Manual View and then return to the Script View.
