On Wed, Jun 27, 2012 at 9:22 AM, Andrew Parker <[email protected]> wrote:
> First off, we need to be careful with terminology. An acceptance test is a > test that is worked out with a stakeholder in order to come to a common > understanding of what it means for the work to be done. Acceptance tests can > deal with the system at any level of integration so long as they clearly > express the desires of that stakeholder. We create user stories at the beginning of each project, and our goal is for this to be turned into acceptance tests. It's a good sanity check, since an unspecific or overly-broad user story can't easily be tested, and a too-granular user story isn't an appropriate acceptance test. This is one of the big values that engineers provide to UX and product: are the user stories real and actionable, or are they too hand-wavy? r -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
