describe User do
it { should validate_presence_of(:email) }
pending “should raise an error when email is blank and record is
saved with false option”
end
Then I put pending inside it like one given below and it worked.
describe User do
it { should validate_presence_of(:email) }
it “” do
pending “should raise an error when email is blank and record is
saved with false option”
end
end
I know that rspec is well thought out . Then why rspec is forcing me
to put empty it around pending line. Why can’t I just say that
something is pending and I will get to it later.
Then I put pending inside it like one given below and it worked.
describe User do
it { should validate_presence_of(:email) }
it “” do
pending “should raise an error when email is blank and record is
saved with false option”
end
end
Use an it with no block:
it “should raise an error when email is blank and record is saved with
false option”
I like how in rspec I can say context when I mean context and describe
when I mean describe. Going by that principal here I should have been
allowed to say pending when I mean pending and I should not be forced
to use it which would come in report as pending.
It is nitpicking but paying attention to such detail has made rspec so
great. Just a fresh perspective since I am trying out rspec for the
first time.
I like how in rspec I can say context when I mean context and describe
when I mean describe. Going by that principal here I should have been
allowed to say pending when I mean pending and I should not be forced
to use it which would come in report as pending.
It is nitpicking but paying attention to such detail has made rspec so
great. Just a fresh perspective since I am trying out rspec for the
first time.
In rspec-2 you can say pending like this:
describe ‘something’ do
context ‘in some context’ do
pending ‘it does something or other’