From: Liam M. <lm...@wp...> - 2004-12-21 03:02:20
|
Rally's glossary definition of 'acceptance' is "An activity whereby the customer accepts the validity of a software functionality as a partial or complete performance of a stated system behavior." Whose job is it to do acceptance testing, then? It seems that that kind of thing would be Professor Pollice's job- we do functional testing etc., Gary does acceptance testing to make sure we've got the same goals. Does that sound right, or am I thinking of something totally different? Should we 'hire' a new 'customer'? It seems that the XP Way is to have someone external do the acceptance testing. Liam |