In order to test whether the article has been deleted, go back to the list and see if it's still there. Doing this insulates your tests from refactoring, and only tests things that are visible through your interface (i.e. things you care about). -- Yehuda
On Sun, Oct 19, 2008 at 10:33 PM, oleg dashevskii <[EMAIL PROTECTED]>wrote: > Matt, > > I looked at your code and noticed that you don't test what happens on an > article, only responses. > > E.g. in "a successful DELETE", :given => "a article exists" you check only > for a redirect, but not if the article has really been deleted. > Same in "PUT" - has or hasn't article been really updated is not checked. > > Was this done intentionally? If yes, why? > > > 2008/10/20 Matt Aimonetti <[EMAIL PROTECTED]> > >> hmm these example specs by Yehuda where just (old) stuff we were playing >> with, check my specs instead, tested against 1.0 RC2 >> >> http://gist.github.com/17973 >> >> -Matt >> >> >> On Sun, Oct 19, 2008 at 4:35 PM, Per Melin <[EMAIL PROTECTED]> wrote: >> >>> >>> 2008/10/19 Ashley Moran <[EMAIL PROTECTED]>: >>> > Can anyone show me the best/a good way to write a spec for this? Any >>> > help for a Merb n00b much appreciated. >>> >>> Have a look at these example specs by Yehuda: >>> http://gist.github.com/14910 >>> >>> >>> >> >> >> > > > -- > Oleg. > > > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
