During all my testing, the most recurring problem i've encountered is the fact that Katalon goes through the script way too fast and elements don't have the time to load properly. Then you get a "not found" error and you have to go back and :
- Use a "wait for..." command, which is nice but does't always work either (making test results not very reliable, since sometimes a script will validate, sometimes it will false-fail)
- Use a "Delay" command, which has so far been the best solution but it's annoying to drop "Delay" every 3 lines of script
- Use a project-wide global Delay, which also works but makes the script super slow since you can't set it to lower than 1 second
It would be nice to have Katalon be more intelligent in the way it executes actions, especially "click" or "send text" ones. I was wondering why does the "wait for element clickable" for example even exist, why isn't it always included in a "click" or any other command that directly interacts with an object? Maybe keep the "wait for" commands for cases where you really NEED to verify the state of an object, but otherwise include them all in the appropriate interaction commands?
Also, it might be very useful to be able to automatically retry a step/action during execution. I know it can be done with code but considering how often things take a while to load on a website because of bad connection, low-power dev/testing servers, browser issues etc, it'll be too much a hassle to individually "retry" all your actions.