Difference between revisions of "AcceptanceTesting"

From CitconWiki
Jump to navigationJump to search
(New page: Business people and testers collaborating Top 5 Reasons why teams fail with acceptance testing #1 No collaboration #2 Focusing on 'how' not on 'what' #3 Tests unusable as live document...)
 
m
Line 3: Line 3:
 
Top 5 Reasons why teams fail with acceptance testing
 
Top 5 Reasons why teams fail with acceptance testing
  
#1 No collaboration
+
# No collaboration
 
+
# Focusing on 'how' not on 'what'
#2 Focusing on 'how' not on 'what'
+
# Tests unusable as live documentation
 
+
# Expecting acceptance tests to be a full regression suite
#3 Tests unusable as live documentation
+
# Focusing on tools
 
 
#4 Expecting acceptance tests to be a full regression suite
 
 
 
#5 Focusing on tools
 

Revision as of 05:11, 19 September 2009

Business people and testers collaborating

Top 5 Reasons why teams fail with acceptance testing

  1. No collaboration
  2. Focusing on 'how' not on 'what'
  3. Tests unusable as live documentation
  4. Expecting acceptance tests to be a full regression suite
  5. Focusing on tools