We have had a really great integrated javascripting testing in our very
large, very javascripty Sinatra application. Our testing setup uses a
custom version of harmony (http://github.com/baccigalupi/harmony), that
reduces the out of control memory we were seeing in the original gem.
The trade off h
David Chelimsky wrote in post #981651:
I am happy to get back to you about the documentation a little later. I
want to take the time to fully describe the problems we had.
> Please let me know what is not yet documented on the following pages:
>
> http://relishapp.com/rspec/rspec-core/v/2-5/file/
Kane Baccigalupi wrote in post #981670:
> We can try a global, but it isn't an ideal situation.
So, we did replace @dom with $dom. That meant we could go back to doing
no manual garbage collection, and in fact we didn't even have to set the
global to nil between test files.
Doesn
David Chelimsky wrote in post #981667:
> The instance vars in after(:all) are copies, so setting them to nil
> there has no real effect. This was true in rspec 1 as well, so what you
> are experiencing is unrelated.
>
> As a workaround, how about setting a global? Not a perm solution, but
> might
Hi,
I have been a bad TDD developer and developed before testing. My code is
working fine, but I have been writing tests because it is the right thing to
do. I am running into trouble with some controller methods that are saved in
a separate lib module and included in the application.rb file. I st
