+100 on test first. Good reading on software development in general includes "The Pragmatic Programmer", "Extreme Programming Explained: 2nd Edition" and Mike Cohn's "Agile Estimating and Planning". There are a million good books, but those three wouldn't be a bad start to any programmers bookshelf.
There's also a great rspec book out there for the details of implementing testing in Ruby using rspec and cucumber. http://www.pragprog.com/titles/achbd/the-rspec-book Best Wishes, Peter On Nov 2, 2010, at 8:49 AM, radhames brito wrote: > on sure thing you have wrong is this > > 3. Coding > 4. Testing > > it should be > > 3. write test > 4. fails test > 5. write code > 6. pass test > > repeat as necessary. > > Also try to convert what the costumer tells you into stories, and let that > guide your test and consequently your code. Functionality should be almost > the same( or require minor changes) no matter the appearance of the site, > like peter said try to "get most of the way there functionally before getting > locked into designs". > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
