On Fri, Feb 19, 2010 at 6:53 PM, drewB wrote:
> I am using autotest with RSpec (autospec) and for some reason it
> doesn't monitor files under the integration folder. Does anyone know
> how to config autotest to monitor additional paths? I tried playing
> with add_mapping in my .autotest but was
I am using autotest with RSpec (autospec) and for some reason it
doesn't monitor files under the integration folder. Does anyone know
how to config autotest to monitor additional paths? I tried playing
with add_mapping in my .autotest but was not able to get it to work.
Thanks!
P.S. I know that
On Fri, Feb 19, 2010 at 8:13 PM, Pat Maddox wrote:
> I disagree with the crowd on the basis that these examples are lazy. Very
> close to what I do though.
>
> Imagine you had one other example in there:
>
> it "should assign the post to the view" do
> post :create
> assigns[:post].should == @
I disagree with the crowd on the basis that these examples are lazy. Very
close to what I do though.
Imagine you had one other example in there:
it "should assign the post to the view" do
post :create
assigns[:post].should == @post
end
Then you wouldn't really need the other should_receive
Look in spec/spec_helper.rb for the configuration block, and hook up your
custom stuff there:
Spec::Runner.configured do |config|
config.before(:each) { AfterFixturesLoaded.custom_stuff1 }
config.after(:each) { AfterFixturesLoaded.custom_stuff1 }
end
Pat
On Feb 16, 2010, at 8:48 AM, Ben F
I kind of follow a similar principle here. Many times I will write app
code because in not sure how to pull of the functionality I'm try to
do. Once I can confirm that I'm getting the expected results, I take a
mental note of what I did, remove the code, and drive it out again
with the spec
On 19 Feb 2010, at 08:59, Erik Pukinskis wrote:
Hello Specmeisters!
I have a bit of a philosophical question for the TDD witches and
wizards out there. I'm working on some code that is really
churning... It's doing complicated calculations, but the actual
desired results are a moving target.
hi there,
well I'm not a meister myself, but spec-ing something you don't know the
outside result is a bit hard for me.
I normally work in two modes:
* hacking mode: that's when I'm trying to "see" if I can do something, if
the result will run, getting to know the problem and such. In these mode I
Testing should answer this question for you, regularly: How do you
know it works?
Courtenay
On Fri, Feb 19, 2010 at 12:59 AM, Erik Pukinskis
wrote:
> Hello Specmeisters!
>
> I have a bit of a philosophical question for the TDD witches and
> wizards out there. I'm working on some code that i
Hello Specmeisters!
I have a bit of a philosophical question for the TDD witches and
wizards out there. I'm working on some code that is really
churning... It's doing complicated calculations, but the actual
desired results are a moving target. The acceptable values, and even
the structure of the
10 matches
Mail list logo
