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, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > *Sent:* Monday, August 06, 2007 11:15 AM > *To:* [email protected]; 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, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > 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
