[Webtest] cruisecontrol

[webtest@lists.canoo.com]

The doc for <clickbutton> shows that it supports
html like this:

<INPUT type=3D"submit"  value=3D"doIt" />


My html button looks a bit different:
	<button type=3D"submit"  ID=3D"idSearchButton" CLASS=3D"button">
                        Search
	</button>

What should my <clickbutton> look like for the above html?

-----Original Message-----
From: Dierk Koenig [mailto:dierk.koenig@canoo.com]
Sent: Thursday, July 25, 2002 5:50 AM
To: webtest@lists.canoo.com
Subject: RE: [Webtest] cruisecontrol


Hi Eric,

for monitoring purposes at canoo we use "BigBrother", which can be
configured quite extensively.

CruiseControl has a fairly different target.

We haven't used WebTest for monitoring so far, although I expect it
to be possible, e.g. in cooperation with BigBrother.
On the other hand, we use WebTest to assert Application functionality
that is not likely to break after the running installation has
passed the test once. We only monitor for availability after that.

For application logic is possible to break after source code changes,
we check for those breaks using WebTest after each change commited to
the repository. This is done using CruiseControl.

cheers
Mittie

> -----Original Message-----
> From: webtest-admin@lists.canoo.com
> [mailto:webtest-admin@lists.canoo.com]On Behalf Of EPugh@upstate.com
> Sent: Mittwoch, 24. Juli 2002 22:56
> To: webtest@lists.canoo.com
> Subject: RE: [Webtest] cruisecontrol
>
>
> Not actually sure who I met, when I went back and reread the
> emails!  What I
> am trying to do (and maybe there is a better tool out there) is to
verify
> that status of a couple different web based applications.
>
> We have used Whatsup gold relatively successfully to monitor services,
> however, when it comes to monitoring a web application, it is very
clunky.
> It seems that the scripts that I run to validate my various
> builds, if they
> where made non intrusive (not changing any significant data etc
> in the app)
> would also be the perfect way to verify that everything in a web app
is
> working, from database access, to ldap logins.  However, I need a
> framework
> to trigger the script that browses the website, and if there is a
failure,
> to generate an email.  Additionally, I would like to navigate multiple
> different sites, and get an email whenever each one dies.
>
> It seems (though I haven't dug into it) that CC could be that
> engine, but I
> am not sure if there aren't other "schedulers" that are more
Ant/webtest
> friendly.
>
> Or, if there are other better tools out there that could do what
WebTest
> does...
>
> Eric
>
> -----Original Message-----
> From: Dierk Koenig [mailto:dierk.koenig@canoo.com]
> Sent: Wednesday, July 24, 2002 9:01 AM
> To: webtest@lists.canoo.com
> Subject: RE: [Webtest] cruisecontrol
>
>
> Hi Eric,
>
> I'm not sure, whether you mean David or me with "you". :-)
>
> However, there is a CruiseControl running that instantly builds
> WebTest whenever there is a change in the CVS.
>
> You will find the corresponding cruise.xml that steers the
> CruiseControl in the root of the CVS module as well as other
> concerned files like emailmap.properties and cruisecontrol.properties.
>
> The contents is supposed to be self-explaining :-)
>
> The CruiseControl used for building and selftesting WebTest doesn't
> differ at all from setups used for any other Web Application.
>
> cheers
> Mittie
>
> > -----Original Message-----
> > From: webtest-admin@lists.canoo.com
> > [mailto:webtest-admin@lists.canoo.com]On Behalf Of EPugh@upstate.com
> > Sent: Mittwoch, 24. Juli 2002 14:34
> > To: webtest@lists.canoo.com
> > Subject: RE: [Webtest] cruisecontrol
> >
> >
> > I would love to see your CrusieControl stuff.  While we are using
> > Webtest as
> > a User Acceptance, and QA step, we also need to monitor the site in
> > production.  Since Webtest makes navigating a site so easy,
> coupled with a
> > good clean CruiseControl tool, it could be very valuable.
>
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
>

_______________________________________________
WebTest mailing list
WebTest@lists.canoo.com
http://lists.canoo.com/mailman/listinfo/webtest