t; bunch of "testing" activity which isn't really solving any real problems
>> but is certainly slowing down the flow. Please let me clear - I am not
>> challenging the _requirements_ of the traditional testing process (e.g.
>> ensuring quality), I am
ear - I am not
> challenging the _requirements_ of the traditional testing process (e.g.
> ensuring quality), I am claiming the way most people do it is incredibly
> expensive and inefficient.
>
> I can hear the internet taking a breath saying "No!, he didn't just go
> there
adable English textual specifications
> which everybody collaborates on. The geeks do their thing (using Ruby,
> Clojure, groovy, Scala, Selenium, A.N.Other etc.) to execute those same
> specs.
>
> On Monday, 27 October 2014 04:21:07 UTC, David Mitchell wrote:
>>
>> H
Hi group,
Apologies for the somewhat cryptic subject line - I'll try to explain...
Apologies also for the length of the post, but I'm sure others will hit
the same problem if they haven't already done so, and hopefully this
discussion will help them find a way out of a sticky situation.
We've
