On Tue, Feb 17, 2009 at 10:32 PM, Ashley Moran
wrote:
>
> On 15 Feb 2009, at 19:47, Ben Mabey wrote:
>
>> To illustrate what Zach is saying here is an example I used on the wiki[1]
>> before:
>>
>> # Global setup
>> ActionMailer::Base.delivery_method = :test
>> ActionMailer::Base.perform_deliverie
On Tue, Feb 17, 2009 at 8:42 PM, Yi Wen wrote:
> ah! sorry, my bad. Thanks!
No worries - I always just read the code first too :)
>
> On Tue, Feb 17, 2009 at 6:56 PM, David Chelimsky
> wrote:
>>
>> On Tue, Feb 17, 2009 at 6:25 PM, Yi Wen wrote:
>> > Sorry for the spam, I relized there was a ty
ah! sorry, my bad. Thanks!
On Tue, Feb 17, 2009 at 6:56 PM, David Chelimsky wrote:
> On Tue, Feb 17, 2009 at 6:25 PM, Yi Wen wrote:
> > Sorry for the spam, I relized there was a typo. It should be
> >it {should validate_presence_of(:login)}
> > It still didn't work
>
> Scrolling up a bit
according to this post:
http://blog.davidchelimsky.net/2009/1/13/rspec-1-1-12-is-released
I should be able to write:
describe User do
it {should valdate_presence_of(:login)}
end
with rspec 1.1.12
But I got:
NO NAME
undefined method `valdate_presence_of' for
#
Hi Yi,
I believe you're
On Tue, Feb 17, 2009 at 6:25 PM, Yi Wen wrote:
> Sorry for the spam, I relized there was a typo. It should be
>it {should validate_presence_of(:login)}
> It still didn't work
Scrolling up a bit ...
"There are a few matcher libraries out there like
rspec-on-rails-matchers that provide m
Sorry for the spam, I relized there was a typo. It should be
it {should validate_presence_of(:login)}
It still didn't work
On Tue, Feb 17, 2009 at 6:04 PM, Yi Wen wrote:
> Hello,
>
> according to this post:
> http://blog.davidchelimsky.net/2009/1/13/rspec-1-1-12-is-released
>
> I should b
Hello,
according to this post:
http://blog.davidchelimsky.net/2009/1/13/rspec-1-1-12-is-released
I should be able to write:
describe User do
it {should valdate_presence_of(:login)}
end
with rspec 1.1.12
But I got:
NO NAME
undefined method `valdate_presence_of' for
#
What did I do it wrong?
On Tue, Feb 17, 2009 at 5:14 PM, Oliver Barnes
wrote:
> sorry to bump this up, I am the only one experiencing this problem?
> anybody else running cucumber in other languages?
Oi Oliver,
Poderia ver o codigo aqui:
http://github.com/aslakhellesoy/cucumber/blob/e1afbf1908fdb3867d857478847403abeedd
On Tue, Feb 17, 2009 at 3:32 PM, Ashley Moran
wrote:
>
> On 15 Feb 2009, at 19:47, Ben Mabey wrote:
>
>> To illustrate what Zach is saying here is an example I used on the wiki[1]
>> before:
>>
>> # Global setup
>> ActionMailer::Base.delivery_method = :test
>> ActionMailer::Base.perform_deliveries
On 15 Feb 2009, at 19:47, Ben Mabey wrote:
To illustrate what Zach is saying here is an example I used on the
wiki[1] before:
# Global setup
ActionMailer::Base.delivery_method = :test
ActionMailer::Base.perform_deliveries = true
Before do
# Scenario setup
ActionMailer::Base.deliveries.c
sorry to bump this up, I am the only one experiencing this problem?
anybody else running cucumber in other languages?
2009/2/14 Oliver Barnes :
> Hello,
>
> I've just installed cucumber 0.1.99, and it looks like the Portuguese
> step keywords aren't recognized for some reason. I'm following this
>
On Fri, Feb 13, 2009 at 5:20 PM, Nathan Wilmes wrote:
> A few of our tests attempt to test controllers with production-style
> rescuing. Before the current rspec/Rails 2.2.2 combo, it was fairly easy to
> set up for these tests:
>
> it "should throw a 404 for strange actions" do
> controller.us
On Feb 17, 2009, at 3:27 PM, Lenny Marks wrote:
Forgive the long post, just looking for input/advice/alternate
opinions..
Like many I think that going through the exercise of framing user
requests in Cucumber terms(Features, Scenarios..) really helps
facilitate necessary conversations an
Forgive the long post, just looking for input/advice/alternate
opinions..
Like many I think that going through the exercise of framing user
requests in Cucumber terms(Features, Scenarios..) really helps
facilitate necessary conversations and avoid time wasted implementing
the wrong thing(
>
> Ok, so I tried just sticking an "ENV['HTTPS'] = 'on'" in my
> spec/spec_helper.rb file and re-running my spec suite. Looks like this is
> not enough in itself, as I got about 77 spec failures, all of them
> apparently caused by "ssl?" returning false and producing unwanted
> redirects.
>
Rails
On Mon, Feb 16, 2009 at 8:21 PM, Phlip wrote:
> David Chelimsky wrote:
>
>> When RSpec is used as customer facing, they see the docstrings
>> (strings passed to describe() and it()), not the internal code. That's
>> for developers.
>
> Then why the .should stuff? I'm a developer - technically - an
16 matches
Mail list logo
