-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bret Pettichord
Sent: 22 February 2007 06:46 AM
To: wtr-general@rubyforge.org
Subject: Re: [Wtr-general] Watir.. close, but not close enough
John Lolis wrote:
I don't feel that its a problem Watir needs
Walter Kruse wrote:
I just wish the Win32-GUITest library could get the same amount of
attention. I've had lots of success with Perl's version of this lib.,
and would like to do that testing in Ruby now.
Maybe you could give it some attention. Seriously, there is no one to do
this stuff
On 2/22/07, Walter Kruse [EMAIL PROTECTED] wrote:
Bret,
I had a look long ago at Piotr Kaluski's very detailed docs for Perl's
Win32GuiTest
(http://www.piotrkaluski.com/files/winguitest/docs/winguitest.html).
He even lists some C code examples. I'm afraid C is a little beyond
me...
Wayne
Indeed. Watir's strength for us was that we couldn't afford a huge application
and all the time and training that entails, and Watir allowed us to put
together a pretty comprehensive set of tests for our few websites.
Creating a general-purpose framework would probably make it as complex as
John Lolis wrote:
I don't feel that its a problem Watir needs to solve. If the community really
did want some framework I think it would be a project separate from Watir.
I'm not even sure a project like that would work. Every application that
needs testing is probably going to need a
I think the problem for the OP is that we don't have
good
examples/documentation describing this approach.
I don't feel that its a problem Watir needs to solve. If the community really
did want some framework I think it would be a project separate from Watir. I'm
not even sure a project
I'm not entirely sure what you mean by being unable to reference scripts, but I
split my tests into:
1 script with helper functions such as GoToURLAndExpectText for example
1 script with the header type declarations in it, URL's, usernames etc
X several scripts with various parts of the app
Cylindric wrote:
I'm not entirely sure what you mean by being unable to reference scripts, but
I split my tests into:
1 script with helper functions such as GoToURLAndExpectText for example
1 script with the header type declarations in it, URL's, usernames etc
X several scripts with various
Critical commentary follows:
[i]I have taken a leap into watir and I must say that at first glance it was
fun, easy and usable. However, when I needed a more complicated and managed
solution it fell flat. Watir provides an easy and simple way to access DOM
elements and complete user (through
