[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-swt-dev] swt.Robot?
|
How about an interface to native GUI event queue. Which would allow you to
write test cases manipulating SWT applications as well as native
applications. A number of automation queries would probably be to
information only maintained by SWT, but that could be served by special
message (event) handlers implemented in the platform dependent layer.
----- Original Message -----
From: "Thomas L Roche" <tlroche@xxxxxxxxxx>
To: <platform-swt-dev@xxxxxxxxxxx>
Cc: <java-gui-testing@xxxxxxxxxxxxxxx>
Sent: Tuesday, December 24, 2002 7:45 PM
Subject: Re: [platform-swt-dev] swt.Robot?
> Mike_Wilson@xxxxxxxxxx Tue, 24 Dec 2002 09:37:11 -0500
> > I realize this isn't exactly what you are asking for,
>
> :-/
>
> > but I did see this in the R2.2 plan:
>
> http://www.eclipse.org/eclipse/development/eclipse_project_plan_2_2.html
>
> > " ( new) Support automation of common tasks. To make it easier for
> > users to automate common and repetitive tasks, the user should have
> > a simple way of recording the sequence of actions as they perform
> > them. The recording can be edited, saved persistently, and played
> > back under similar circumstances in the same or later session, or
> > possibly another workspace. [Platform UI, Platform Core, Platform
> > Text, JDT Core, JDT UI, PDE] "
>
> Recording is but a small step towards the functionality that awt.Robot
> provides to Swing users. What I want is what they've got now: the
> ability to write automated, JUnit-integrated test cases. E.g.
>
> http://abbot.sourceforge.net/doc/Tutorial-2.html
> http://jfcunit.sourceforge.net/loginscreenexample.html
>
> Timothy Wall notes the problem with "raw" record/playback:
>
> http://abbot.sourceforge.net/doc/api/overview-summary.html <edited>
> > GUI layouts tend to change over time. A raw event recorder/playback
> > mechanism will likely break if you're operating in absolute
> > coordinates[. Also,] different platforms generally size their
> > components differently, so [record/playback] may not work
> > cross-platform. [A good test tool shouldn't] care where components
> > are positioned, as long as it can look them up dynamically with a
> > few tagging identifiers.
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
>
>
