• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Role of Testing Automation tools in Agile Testing

 
Ashutosh Sharma
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Lisa & Janet,

Does Automation Testing Tools like RFT, QTP etc are Integrated part of Agile Testing? Or in particular whats the role of Testing Automation Processes in Agile Testing.

Regards,
Ashutosh Sharma
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Test automation is key in agile projects. Its what watches your back as your focus shifts from one user story to the next and prevents you breaking the current functionality by adding new functionality.
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In fact, in "Testing Extreme Programming", Lisa had a chapter on manual testing that consisted of just one sentence: "No manual tests."
 
Jeff Langr
author
Ranch Hand
Posts: 799
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ilja Preuss wrote:In fact, in "Testing Extreme Programming", Lisa had a chapter on manual testing that consisted of just one sentence: "No manual tests."


Which is a pretty outrageous stance, even for someone like me who has been doing XP/agile for almost ten years. It's always a good goal to push toward as much automation as possible, but completely unrealistic in most environments and even dangerous in some. One way to view automation is to make more time for the exploratory testing that needs to occur.

Even Ward Cunningham believes in the use of exploratory testing:

"Because an agile development project can accept new and unanticipated functionality so fast, it is impossible to reason out the consequences of every decision ahead of time. In other words, agile programs are more subject to unintended consequences of choices simply because choices happen so much faster. This is where exploratory testing saves the day. Because the program always runs, it is always ready to be explored."


(see also http://www.informit.com/articles/article.aspx?p=405514, which is the article where I found this quote)

I'm hoping there is a bit more discussion and fewer one-line dismissals in this book.

Jeff L.
 
Jeff Langr
author
Ranch Hand
Posts: 799
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And maybe I'm not reading enough into that one line, or don't have enough context. "No manual tests" might have been better written "no manual test scripts," which seems a reasonable goal.

Jeff
 
Jeff Langr
author
Ranch Hand
Posts: 799
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For some more specifics about the things that you might not want to or be able to automate, Michael Bolton (who I don't agree with on many topics, but who often makes irrefutable points) posted this message a few years ago:

http://newsgroups.derkeiler.com/Archive/Comp/comp.software.testing/2005-09/msg00015.html
 
Lisa Crispin
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jeff Langr wrote:
Ilja Preuss wrote:In fact, in "Testing Extreme Programming", Lisa had a chapter on manual testing that consisted of just one sentence: "No manual tests."


Which is a pretty outrageous stance, even for someone like me who has been doing XP/agile for almost ten years. It's always a good goal to push toward as much automation as possible, but completely unrealistic in most environments and even dangerous in some. One way to view automation is to make more time for the exploratory testing that needs to occur.

Even Ward Cunningham believes in the use of exploratory testing:
...*snip*
I'm hoping there is a bit more discussion and fewer one-line dismissals in this book.

Jeff L.

Hi Jeff,
I later wished our earlier book had said, "No manual regression tests". And even in that case, as the next chapter in Testing XP explains, there are exceptions.

I think you will find a lot of different testing approaches covered in Agile Testing. We emphasize the need for exploratory testing, among other things. We are pleased to have sidebars about ET contributed by Michael Bolton and Jon Hagar.

We do feel automation is key. Without adequate automation, there's no time for exploratory testing in a short agile iteration. We also explain in the book how automation can be used as an aid to exploratory testing, as my team does.
-- Lisa
 
Jeff Langr
author
Ranch Hand
Posts: 799
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Lisa--

Thanks for the clarification; I'm good enough to buy a copy (at Amazon since it's not locally stocked!)

Jeff
 
Ashutosh Sharma
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks everyone for sharing thier experience!!

I am quiet young as compared to you all. I used RFT in my prevois project for a web based pplication. Automate Testing for an application depends very much on how that Application is developed.

Suppose if i change the name of my controls in the application in the next build my scripts will not work on the new build.

It concludes that Application should also be build using Agile Techniques in which we can continously add new features and processes without making much change to the existing ones.

For sure i'll refer this book to learn more about Agile Testing and Role of Test Automation tools in the same.

Thanks Lisa, George!!

Regards,
Ashutosh Sharma

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic