Recently, we’ve been seeing another “feature” of KSE. It’s changing scripts by itself at the arbitrary time just because it “thinks” that // should not be in the beginning of lines but it should be indented. As a result, we are having the following problems:
Push the file with // in the beginning (from the original computer)
Pull the file (from a different computer)
Katalon desides that // should not be in the beginning of lines and modifies the file at the arbitrary time
Push the file with both intentional (3) and unintqentional (4) modifications
Pull the file (to the original computer) and get mulltiple ERRORS which we should waste our time to resolve.
Another problem is that the files are shown as modified even though there was now intentional modifications but we still need to double-ckeck it before comitting.
Who came up with such a beatiful feature? Anyhow. Thanks a lot for that useful “feature” and now can you please let us know how to get rid of it? Thanks again!
Thanks, @Russ_Thomas, yes, I did. To be precise, sometimes I click on Manual view by mistake (I don’t use it) and then switch back to Script view. Subjectively, it looks like it can happen to any file opened in KSE regardless of switching. I’m going to pay more attention to switching.
Actually, I’ve just noticed that any test gets openned in Manual view after clicking on it.
As @Russ_Thomas pointed out, there is a configuration option Preferences > Katalon > Test Case >> Default Open View : Manual View or Script View.
When you upgrade Katalon Studio to a new version, this option will be initialised to “Manual View”. Even if you had this option to be “Script View” in your previous installation, it won’t be carried over while upgrading.
After upgrading Katalon Studio, I always change this option to “Script View”. This is the 1st thing I do after upgrading.
I didn’t notice when exactly it was hapenning. Just saw the “results”. Howerver, I’m not sure that it’s related to switching to “Manual Mode” (as it was noticed by @Russ_Thomas ) only. I’ve seen the same “results” in Keywords, which have no “Manual Mode”:
By the way, despite the differences (produced by KSE, please see an example above), those differences are not highlighted at all in KSE and not detected by using “Next Difference”, ''Previous Difference". Is this expected? Thanks.
The simplest trigger is just OPENING any KEYWORD file that had // at the very beginning of the line. That’s it. Nothing else is needed to totally screw up the file and the collaboration between our team members who are using KSE.
Thanks again, @kazurayam. OUR original problem IS that it didn’t happen before and then it started all of a sudden. So, obviuosly, something was changed in KSE, not on our side cause none of us changed anything (none of us has any idea what should be changed in those settings). Also, by @nam.nguyen’s request I provided the SIMPLEST triger that’s easy to reproduce.It’s quite possible that there are some other triggers.