The Artima Developer Community
Sponsored Link

Java Buzz Forum
Top 10 reasons why teams fail with Acceptance Testing

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
News Manager

Posts: 47623
Nickname: newsman
Registered: Apr, 2003

News Manager is the force behind the news at Artima.com.
Top 10 reasons why teams fail with Acceptance Testing Posted: Sep 24, 2009 10:24 AM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by News Manager.
Original Post: Top 10 reasons why teams fail with Acceptance Testing
Feed Title: testdriven.com
Feed URL: http://feeds.feedburner.com/testdrivennewslinks?news=10&links=10
Feed Description: Your test-driven development community
Latest Java Buzz Posts
Latest Java Buzz Posts by News Manager
Latest Posts From testdriven.com

Advertisement
Another fantastic blog by Gojko Adzic Top 10 reasons why teams fail with Acceptance Testing

Personally, I am leaning towards using the term "Executable Specifications" instead of Acceptance Testing. Note that Gojko mentions this specifically in item 4. Let me know what term you prefer at david@testdriven.com

Read: Top 10 reasons why teams fail with Acceptance Testing

Topic: ComScore, Omniture join up to measure digital audiences Previous Topic   Next Topic Topic: How to find ethernet / MAC address on Linux

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use