[TIP] Declarative style acceptance tests

[Olemis Lang]

On 1/7/14, Ben Finney <ben+python at benfinney.id.au> wrote:
> Michael Foord <fuzzyman at voidspace.org.uk> writes:
>
>> I'm sceptical that any real world customer anywhere, ever (almost),
>> actually reads acceptance tests - let alone writes any.
>
> If you'll accept my testimony, I have worked on several successful
> commercial projects where the customer got involved in writing the
> acceptance test assertions in formal machine-parseable language.
>

I second that , and users have been very satisfied with the results
because they feel like they are part of the dev team (somehow) in
control and with perfect understanding of the (part of the) process
(they are involved with) since the communication barriers are almost
gone . They can play an active role to *really* influence the outcomes
of the dev process .

We've even tried methods (successfully at some extent) to gather user
input in (almost) natural English and extract (automatically) the DB
structure .

> They did so in large part *because* those acceptance test assertions
> were actually used as input to our automated test suite, and reports
> automatically generated for how many assertions were passing as the
> development progressed.
>

+1

[...]

-- 
Regards,

Olemis - @olemislc

Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: