[jbosstools-issues] [JBoss JIRA] (JBIDE-12953) Investigate usage of Windows Tester Pro for UI Tests

[ https://issues.jboss.org/browse/JBIDE-12953?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-12953: ----------------------------------- Description: {quote} During EclipseCon Europe, I chatted with a guy who's a pure technology-agnostic guy (not a guru, not an evangelist, just a user who gives his user story in an objective way). He used to use SWTBot to write tests, but he started using Google WindowTester Pro [1] tool since it was released under EPL by Google [2]. He told me that WindowTester Pro has a bot API quite similar to SWTBot, compatible with JUnit and Tycho; and the most interesting point is that Window Tester contains a recorder which allows to record tests pretty easily. This could help us to write tests, but also be used by end-users to provide their failing scenarios as WindowTester scenarios. The recorder simply logs all SWT events and tries to turn meaningful sequences of Events to user-grained UI operations (such as click). I was reported that 90% of code written by the recorder is good for industrial testing, the 10 remaining % requires some refactoring and Java coding; and that using WindowTester Pro takes half the time as recording+writing SWTBot tests to provide exactly the same thing, with the same level of (re)usability and maintainability. {quote} was: {quote:Mickael} During EclipseCon Europe, I chatted with a guy who's a pure technology-agnostic guy (not a guru, not an evangelist, just a user who gives his user story in an objective way). He used to use SWTBot to write tests, but he started using Google WindowTester Pro [1] tool since it was released under EPL by Google [2]. He told me that WindowTester Pro has a bot API quite similar to SWTBot, compatible with JUnit and Tycho; and the most interesting point is that Window Tester contains a recorder which allows to record tests pretty easily. This could help us to write tests, but also be used by end-users to provide their failing scenarios as WindowTester scenarios. The recorder simply logs all SWT events and tries to turn meaningful sequences of Events to user-grained UI operations (such as click). I was reported that 90% of code written by the recorder is good for industrial testing, the 10 remaining % requires some refactoring and Java coding; and that using WindowTester Pro takes half the time as recording+writing SWTBot tests to provide exactly the same thing, with the same level of (re)usability and maintainability. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira