Your very welcome :) 2008/12/7 Dan North <[EMAIL PROTECTED]>
> Hooray! I've been looking for a reference for that quote for years! Thanks > Andrew. > > > 2008/12/7 Andrew Premdas <[EMAIL PROTECTED]> > > "There are two ways of constructing a software design: One way is to make >> it so simple that there are no obvious deficiencies, and the other way is to >> make it so complicated that there are no obvious deficiencies. The first >> method is far more difficult" >> >> C. A. R. Hoare, Professor of Computing, Oxford University (and inventor of >> the quicksort algorithm >> >> No one said its easy :) >> >> >> 2008/12/7 James Byrne <[EMAIL PROTECTED]> >> >>> Andrew Premdas wrote: >>> > >>> > So my initial scenario might be >>> > >>> > When I create a new improvement >>> > I should see a confirmation >>> > >>> > and my second scenario might be >>> > >>> > Given there are some improvements >>> > I should be able to view improvements >>> > >>> > Finally have a think about whether this feature is actually important >>> > enough >>> > to be doing first. >>> >>> The question arises, how does one tell what is important enough to begin >>> with? I am trying to form a robust mental pattern for employing BDD and >>> I keep running up against the tension between what I already believe to >>> be necessary to provide from my prior knowledge and what point to begin >>> with in features to cause this to be expressed. The examples that I >>> have found regarding how to use BDD features run the gamut from >>> specifying model attributes and data normalization to macro statements >>> of the form: >>> >>> Given I have a web application >>> When I visit the application url >>> Then I should see a welcome message >>> And I should see a sign in request >>> >>> etc. >>> >>> So, the question I have is: >>> >>> Given I have an application design document >>> When I specify the design using BDD >>> Then I should first begin with ?????? >>> >>> -- >>> Posted via http://www.ruby-forum.com/. >>> _______________________________________________ >>> rspec-users mailing list >>> rspec-users@rubyforge.org >>> http://rubyforge.org/mailman/listinfo/rspec-users >>> >> >> >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
