I’ve just recently hit the same issue. There is basically a “hole” in the hierarchy and scoping mechanism provided by Katalon which I hope they fix:
There needs to be a way to create variables that have suite-scope. GlobalVariables are project-scope, test-case variables are local to a test case, but we need a scope that is maintained across an entire suite. Only then will writing test suites which work across multiple domains become easy.
This:
WebUI.openBrowser(yourFullURL)//Navigate to relativeURL based on your full URLWebUI.navigateToURL(yourFullURL + '/view1')
does not work. There is no way to communicate the dynamic value in yourFullURL to 2, 3, N, different suites. We need Suite-Scope variables.
I’ve just recently hit the same issue. There is basically a “hole” in the hierarchy and scoping mechanism provided by Katalon which I hope they fix:
There needs to be a way to create variables that have suite-scope. GlobalVariables are project-scope, test-case variables are local to a test case, but we need a scope that is maintained across an entire suite. Only then will writing test suites which work across multiple domains become easy.
This:
WebUI.openBrowser(yourFullURL)//Navigate to relativeURL based on your full URLWebUI.navigateToURL(yourFullURL + '/view1')
does not work. There is no way to communicate the dynamic value in yourFullURL to 2, 3, N, different suites. We need Suite-Scope variables.
You can put the URL in a data file and bind it to the test case in the suite, as a workaround
You can put the URL in a data file and bind it to the test case in the suite, as a workaround
Or, do like I did and import all your “globals” from an external json file and manage the file yourself.
Yes, that is also an option, i use it for a different case,.
But I am not importing globals, I created a dummy test data with default values and i am parsing it before the execution to replace with the actual values. This can be used on globals file too, is just an xml