I really agree with the topic starter. I've always done the rspec testing
with all layers in isolation, a bit like the first example.
Now for my latest project I went a bit for a more TDD approach, sending a
request to a controller and testing the full stack, including the dynamic
bits of the layou
Question is, would you duplicate the specs for all the classes that include
a certain module (through shared behaviour for example), or would you use
one set of specs for just the module, and specify that a class should
include that module?
On Sun, Feb 24, 2008 at 12:19 AM, Pat Maddox <[EMAIL PROT
0:51 PM, M. Edward (Ed) Borasky <[EMAIL PROTECTED]> wrote:
> Matthijs Langenberg wrote:
> > Hello everybody,
> >
> > I've been using RSpec as a tool to create web applications for some time
> > now, in Rails, and using plain Ruby with WEBrick as well. The tool
ork somewhere, to capture the actual calls to this toolkit to know if
our code is doing the right thing. At least, that's how I see it currently.
But how could that be done?
Regards,
Matthijs Langenberg
___
rspec-users mailing list
rspec-users@rubyfor
They are really cool indeed, can't wait to give it a try on a new project.(or
force it upon an existing project for that matter ;-))
On 10/25/07, Tom Stuart <[EMAIL PROTECTED]> wrote:
>
> > Step 3: Let her open the box … no, that's not it …
>
> I'm ashamed to admit it, but I actually laughed out l
ur or am I taking a wrong
approach?
I feel the need for some small, simple, clean example programs, to take a
look through.
Maybe, I just need to put my current pet project online and let people shoot
at it.
- Matthijs
On 9/30/07, Pat Maddox <[EMAIL PROTECTED]> wrote:
>
> On 9/29/0
Many posts on this list are about using RSpec with Rails and that's the way
I'm also using RSpec all the time.
Unfortunately there isn't that much info about using RSpec for standalone
Ruby projects.
I must admit I'm really having a hard time writing the very first example(s)
for a fresh standalone
I tend to write a fresh description block for every change in the parameters
for that specific action, because I hate conditionals in the example
describtion, e.g.:
describe SomeController, "handling GET /path/with/param/3" do
it "should do this"
it "should not do this if"
it "should still do th