I had, for historic reasons, a setup on a group of specs:
before(:all) do
@contents = [%w(this that), %w(this other)]
FasterCSV.stub!(:open).and_return(@contents)
@filename = 'test_filename'
end
When I ran the single file (spec spec/transformer/csv_spec.rb), all my
specs passed.
I was disgruntled with the amount of spam I was getting, so I started
setting up accounts for the various mailing lists I listen to. I use
[EMAIL PROTECTED] to read the mail here. Along with the rspec
news that comes over this channel, I'm getting more and more spam
addressed to this same
Thank you, thank you, thank you!
On Oct 5, 2007, at 7:26 AM, David Chelimsky wrote:
> On 10/5/07, Cody P. Skidmore <[EMAIL PROTECTED]> wrote:
>> I just found this one: http://tinyurl.com/3c3mfa
>>
>> David, are there any other RSpec books in the works?
>
> Yes!
>
> Alsak and I are writing Behav
On Sep 7, 2007, at 8:24 AM, Wincent Colaiuta wrote:
> El 7/9/2007, a las 5:36, Jay Levitt escribió:
>
>>> There's a very useful guideline in TDD that says "test YOUR code,
>>> not
>>> everyone elses." The validation library we're testing here is
>>> ActiveRecord's. It's already tested (we hope!
What I've done with this is to just uninstall the gem and commit to
working off of the plugins completely. I've found that with gems in
general, I try to keep them local to the project I'm on, almost as if
they were a plugin. I move them to my project's lib (gem unpack) so
that I've got e
I ran into something really puzzling today. I don't know exactly why
it's happening, but I thought I'd share my experiences.
I started a dummy app just to test an idea outside of the context of
my real work today. So, I quickly get things started:
* rails junk
* cd junk
* ruby script/plugin
