| || |
Java Script instead of 4Test
I was thinking about replacing the scripting language (4Test/OA) with Java Script so the framework can support all the browser including Chrome/Safari and to also support different environment i.e GWT etc.
Is this a good idea?
Right now we need to run against FF 5 or 7 and we have to wait for the next ST release. so I assumed Java scripting can handle all of these issues.
Re: Java Script instead of 4Test
well, I got the reply from ST support...I am posting so others can benefit
We are expecting to see preliminary support for Google Chrome introduced with the release of SilkTest 2011; although I cannot confirm this for certain, this release will be available to customers at the end of the month. I am aware that Safari support has been requested by other customers; but can only say that it is being considered by Product Management. I don't expect Safari support to make it into the 2011 release.
In regards to Google Web Toolkit(GWT) - as it is not explicitly mentioned in the Release Notes, GWT is not officially supported by SilkTest 2010 R2; however when tested in-house the Open Agent was able to identify GWT controls as DOM elements on the webpage, and successfully replay actions against basic GWT controls such as Pushbuttons, Checkboxes and Textfields.
More complex GWT controls such as Grids, Menus and Treeviews will be more challenging due to their complexity, and the fact that they are not fully recognised by SilkTest. One should therefore expect only low level events such as Mouse moves and TypeKeys to be recorded against them; but it may be possible to improve object recognition and coverage of these controls through Class-Mapping, or the creation of new derived classes.
Please let me know if you have any further questions; or whether this support incident can now be closed.