[Webtest] Webtest presentation
Lisa Crispin
Lisa Crispin" <lisa.crispin@gmail.com
Mon, 6 Aug 2007 09:55:53 -0600
------=_Part_112567_737165.1186415753307
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
So are you also selling the idea of automating tests?
I think the white paper on the WebTest site makes some good points that you
could use.
In my experience, the quickest way to get a team to want to automate tests
(and design the app for ease of automation) is to require the entire team to
do the manual regression tests before every release. When programmers feel
they have a 'safety net' of some testers doing manual regression tests, they
aren't as easily 'test infected'.
All that said, if you have no automation at all, the place to start is
really unit testing. That has the best ROI of any test automation. A
two-pronged approach of automating unit tests plus an automated GUI smoke
test worked well for us (and we filled in the middle later).
-- Lisa
On 8/6/07, Luke.Templin@exeloncorp.com <Luke.Templin@exeloncorp.com> wrote:
>
> There's no other automated tools being used on the team or as far as I
> know in the enterprise. The audience for this presentation is 6 developers,
> a Business Analyst, a Project Manager and two Managers, one of which is QA &
> infrastructure manager.
>
>
>
>
>
>
> ------------------------------
>
> *From:* Lisa Crispin [mailto:lisa.crispin@gmail.com]
> *Sent:* Monday, August 06, 2007 11:15 AM
> *To:* webtest@lists.canoo.com; Templin, Luke
> *Subject:* Re: [Webtest] Webtest presentation
>
>
>
> Who's your audience? Programmers, testers,...? Do you already use other
> tools, is there disagreement in which tools to adopt? It's hard to know
> what to suggest without some context.
>
> My team adopted WebTest because it was fairly fast to implement and learn,
> the programmers were not averse to it (as they might be with other tools
> using a scripting language they don't know), it integrated easily with our
> CruiseControl build process, the results reporting is effective, and we
> liked the idea of specifying tests rather than programming them (less likely
> the test will have a bug).
>
> WebTest is one of several tools in our toolbox, it fits a particular need
> we had for GUI smoke tests. The ROI on our regression suite has been
> excellent.
> -- Lisa
>
> On 8/6/07, *Luke.Templin@exeloncorp.com* <Luke.Templin@exeloncorp.com>
> wrote:
>
> I'm making a presentation on Webtest to the team tomorrow. Any suggestions
> on what seems to work to convince others to use the tool and why its better
> than the alternatives.
>
>
>
>
>
> And are there issues with using Webtest to test a ASP.Net website running
> on IIS and using Ajax tools?
>
>
>
> Thanks.
>
>
>
> Luke Templin
>
> **************************************************
> This e-mail and any of its attachments may contain Exelon
> Corporation proprietary information, which is privileged,
> confidential, or subject to copyright belonging to the Exelon
> Corporation family of Companies.
> This e-mail is intended solely for the use of the individual or
> entity to which it is addressed. If you are not the intended
> recipient of this e-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation
> to the contents of and attachments to this e-mail is strictly
> prohibited and may be unlawful. If you have received this e-mail
> in error, please notify the sender immediately and permanently
> delete the original and any copy of this e-mail and any printout.
> Thank You.
> **************************************************
>
> >
>
>
>
>
> --
> Lisa Crispin
> Co-author,
> Testing Extreme Programming
> http://lisa.crispin.home.att.net
>
--
Lisa Crispin
Co-author,
Testing Extreme Programming
http://lisa.crispin.home.att.net
------=_Part_112567_737165.1186415753307
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
So are you also selling the idea of automating tests?<br><br>I think the white paper on the WebTest site makes some good points that you could use.<br><br>In my experience, the quickest way to get a team to want to automate tests (and design the app for ease of automation) is to require the entire team to do the manual regression tests before every release. When programmers feel they have a 'safety net' of some testers doing manual regression tests, they aren't as easily 'test infected'.
<br><br>All that said, if you have no automation at all, the place to start is really unit testing. That has the best ROI of any test automation. A two-pronged approach of automating unit tests plus an automated GUI smoke test worked well for us (and we filled in the middle later).
<br>-- Lisa<br><br><div><span class="gmail_quote">On 8/6/07, <b class="gmail_sendername"><a href="mailto:Luke.Templin@exeloncorp.com">Luke.Templin@exeloncorp.com</a></b> <<a href="mailto:Luke.Templin@exeloncorp.com">Luke.Templin@exeloncorp.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="blue" lang="EN-US">
<div>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">There's no other automated tools
being used on the team or as far as I know in the enterprise. The audience for
this presentation is 6 developers, a Business Analyst, a Project Manager and
two Managers, one of which is QA & infrastructure manager.</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<div>
<div style="text-align: center;" align="center"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="2" width="100%">
</span></font></div>
<p><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;"> Lisa Crispin
[mailto:<a href="mailto:lisa.crispin@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">lisa.crispin@gmail.com</a>] <br>
<b><span style="font-weight: bold;">Sent:</span></b> Monday, August 06, 2007 11:15
AM<br>
<b><span style="font-weight: bold;">To:</span></b> <a href="mailto:webtest@lists.canoo.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">webtest@lists.canoo.com</a>;
Templin, Luke<br>
<b><span style="font-weight: bold;">Subject:</span></b> Re: [Webtest] Webtest
presentation</span></font></p>
</div><div><span class="e" id="q_1143bc5c9d9d2b20_1">
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
<p style="margin-bottom: 12pt;"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Who's your
audience? Programmers, testers,...? Do you already use other tools,
is there disagreement in which tools to adopt? It's hard to know what to
suggest without some context.<br>
<br>
My team adopted WebTest because it was fairly fast to implement and learn, the
programmers were not averse to it (as they might be with other tools using a
scripting language they don't know), it integrated easily with our
CruiseControl build process, the results reporting is effective, and we liked
the idea of specifying tests rather than programming them (less likely the test
will have a bug). <br>
<br>
WebTest is one of several tools in our toolbox, it fits a particular need we
had for GUI smoke tests. The ROI on our regression suite has been
excellent.<br>
-- Lisa</span></font></p>
<div>
<p><span><font face="Times New Roman" size="3"><span style="font-size: 12pt;">On 8/6/07, <b><span style="font-weight: bold;"><a href="mailto:Luke.Templin@exeloncorp.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Luke.Templin@exeloncorp.com</a></span></b>
<<a href="mailto:Luke.Templin@exeloncorp.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Luke.Templin@exeloncorp.com</a>>
wrote:</span></font></span></p>
<div link="blue" vlink="#606420">
<div>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">I'm
making a presentation on Webtest to the team tomorrow. Any suggestions on what
seems to work to convince others to use the tool and why its better than the
alternatives.</span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">And
are there issues with using Webtest to test a ASP.Net website running on IIS
and using Ajax
tools?</span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">Thanks.</span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<p><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">Luke
Templin</span></font></p>
</div>
</div>
<div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;">**************************************************<br>
This e-mail and any of its attachments may contain Exelon<br>
Corporation proprietary information, which is privileged,<br>
confidential, or subject to copyright belonging to the Exelon<br>
Corporation family of Companies.<br>
This e-mail is intended solely for the use of the individual or<br>
entity to which it is addressed. If you are not the intended<br>
recipient of this e-mail, you are hereby notified that any<br>
dissemination, distribution, copying, or action taken in relation<br>
to the contents of and attachments to this e-mail is strictly<br>
prohibited and may be unlawful. If you have received this e-mail<br>
in error, please notify the sender immediately and permanently<br>
delete the original and any copy of this e-mail and any printout.<br>
Thank You.<br>
**************************************************</span></font></p>
</div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;">> </span></font></p>
</div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"><br>
<br clear="all">
<br>
-- <br>
Lisa Crispin<br>
Co-author, <br>
Testing Extreme Programming<br>
<a href="http://lisa.crispin.home.att.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lisa.crispin.home.att.net</a>
</span></font></p>
</span></div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Lisa Crispin<br>Co-author, <br>Testing Extreme Programming<br><a href="http://lisa.crispin.home.att.net">http://lisa.crispin.home.att.net</a>
------=_Part_112567_737165.1186415753307--