I don't know that you NEED to explore script. I am not sure what the capabilities of keyword tests are. But the state of the objects in the application under test will be what they are regardless of whether you are doing keyword tests or script tests. I, personally, am a long time skeptic of any mechanism that is created for the sole purpose of avoiding coding. I have never come across a RAD tool or a WYSIWYG code generator type tool that did not eventually let you down in what you needed to get done. BUT my personal opinion aside, before you scrap keyword testing, look and see if there are mechanisms for waiting for the object that are similar to the WaitVBObject one I mentioned. You click on a a button, the button loads another form, say. You go to click on something on that form. It cannot find the something. AND there is no image in the visualizer. The something that you are attempting to click on may not be there yet. So maybe there is a project property value, or you can wait for a specific object. See
http://support.smartbear.com/screencasts/testcomplete/waiting-for-objects/
