Re: Using GUI Scripting for automated testing?


"zerble" <joe.strazzere@xxxxxxxxx> wrote in message
news:4826fdaa-9885-4c95-968b-3ebf5dfb8673@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 28, 6:35 pm, "Peter Olcott" <NoS...@xxxxxxxxxxxxx>
wrote:

The key benefit of my technology is that is that it
automatically operates aspects of the graphical user
interface in cases where no other tool will function.

I hear what you are saying, but I've yet to see that
demonstrated.

I would think that the design details that I provided
should
have made that apparent.

You haven't provided any design details, let alone
sufficient design
details to support the conclusion that you could operate
GUIs in cases
where no other tool can.

You have made claims of better recognition, and as an
example have
displayed a single image with an unusual font you say
cannot be
recognized by other OCR systems.

What you haven't done is provided a demonstration where
your system
actually operates anything.


Although I have not provided an example of my system
operating anything isn't it obvious that a system that can
"see" the GUI controls on the screen could operate these
controls on the basis of what it "sees" ? I already
provided a concrete example of such a system, Redstone
Software's EggPlant.
http://www.redstonesoftware.com/
http://www.redstonesoftware.com/docs/manuals/index.html
http://www.redstonesoftware.com/docs/mktgmaterials/index.html

Isn't it also obvious that such a system could operate GUI
controls in the cases where these controls do not
programmatically expose their state, since it does not
depend upon a control programmatically exposing its state?

It is also common knowledge that some GUI controls do not
expose their state.
http://www.stickyminds.com/sitewide.asp?Function=edetail&ObjectType=COL&ObjectId=6408

If a system can "see" graphical user interface controls
on
the basis of their pixels in a way similar to the way
that
OCR works (this part should be apparent, if not please
tell
me what is not clear) and this system "understands" how
to
operate these controls (I can't elaborate the details of
this just yet), then it should be obvious that such a
system
could operate most any GUI Control that a human operator
could operate. This would necessarily include controls
that
do not provide any programmatic interface, as well as
controls that do provide a programmatic interface.

If the part about it "understanding" how to operate the
controls is a given, then is it clear how it works
besides
this aspect?

Even if it is a given that your system can "find" a GUI
element (which
you haven't yet demonstrated), it's not at all a given
that your
system can "understand" anything at all about the objects
it can find.

If you could somehow intuit how a GUI object operates
solely based on
the visual appearance, then your system would certainly be
super-
human.


There is no intuition involved.

The
basic system apart from GUI testing will also allow
very
powerful GUI Scripts that take very little development
time.

Very powerful, plus very little development time is
what
all test tool
vendors say.

You haven't demonstrated anything to indicate how you
would make more
powerful scripts, nor how you would reduce the
development
time.

Let's focus on the first part about more powerful scripts
since I can probably provide this explanation without
divulging any details about my second invention. The
second
part can not be elaborated without divulging aspects of
my
second invention so this will have to wait for a while.

Sure.

Pick your favorite programming language, or invent a
pseudo-langugage
if you must.
Post a code snippet showing how that language would be
used to
automate a test without having benefit of your system.
Then post the same code snippet modified to take advantage
of your
system.

I would imagine you could do this without divulging
details about
either of your inventions, right?

And then we can judge how much more powerful it has
become.

No those are details that I can not specify because the
patent is not yet filed.

I think that I have proven at least half of my points above.
The one aspect that I can not yet prove is exactly how much
better my solution is than the solution provided by the
Redstone Software, Eggplant technology. Although I can't yet
prove these points here they are:

(1) My system can automatically operate graphical user
interfaces in at least 500% fewer specified programming
steps. The proof of this will have to wait. A substantial
portion of this benefit is directly derived from the fact
that my system can simultaneously search for at least one
million different graphical objects, and the Redstone
Software Eggplant system is limited to searching for one
graphical object at a time.

(2) Because my system is based on a deterministic finite
automaton capable of searching for at least a million
different graphical objects simultaneously, (when searching
for text this limit is much larger) and the Redstone
Software Eggplant technology can only search for one
graphical object at a time my system can automatically
operate graphical user interfaces in cases with rapidly
changing display screen data, where the Eggplant technology
fails to respond quickly enough.

(3) Because the Redstone Software Eggplant system can only
search for one graphical object at a time, it is entirely
incapable of recognizing any text from display screen
pixels. This limitation makes some operations much more
cumbersome.


.

Relevant Pages

  • Re: Using GUI Scripting for automated testing?
    ... interface in cases where no other tool will function. ... You haven't provided any design details, ... This would necessarily include controls that ... Even if it is a given that your system can "find" a GUI element (which ...
    (comp.software.testing)
  • Re: Top 3 VCL Request
    ... Almost all visual controls are data structures inside. ... itself is modified through the data structure in a threadsafe manner and the ... GUI thread is signalled to catch up when it can. ... like an interface. ...
    (borland.public.delphi.non-technical)
  • Re: Unsafe Names for HTML Form Controls
    ... controls, not just input elements. ... The DOM specification says that a form encompasses behavior of a collection. ... the ECMAScript bindings documents make assertions about the mapping of bracket notation property accessors to collection interface methods. ...
    (comp.lang.javascript)
  • VS.NET and PPC Custom Controls
    ... My project is a set of custom controls for the Compact Framework. ... my controls implement an interface that I created; ... a reference to the interface DLL (taken from the ...
    (microsoft.public.pocketpc.developer)
  • VS.NET 2003 and Custom Controls for Compact Framework
    ... My project is a set of custom controls for the Compact Framework. ... my controls implement an interface that I created; ... a reference to the interface DLL (taken from the ...
    (microsoft.public.vstudio.development)