On 8 Nov 2008, at 06:29, David Beckwith wrote:
Hello my fellow RSpeckers,
I am using the spec command like this:
spec tokyo_record_spec.rb
And the for some reason the should_raise Rspec command is not
happening with my lambda block:
it "should raise a NoSuchAttribute error i
very bizzare but whilst I needed to use this approach to fix one of my
tests, I realised the test before was working without having to make
it a big decimal - go figure :)
it "should return last IR when date > last interest rate" do
@source_bank.ir(Time.n
Hello my fellow RSpeckers,
I am using the spec command like this:
spec tokyo_record_spec.rb
And the for some reason the should_raise Rspec command is not
happening with my lambda block:
it "should raise a NoSuchAttribute error if the attribute 'name'
hasn't been declared yet
thanks Pat - yes I missed it when reading your email - I'd been using
".eql" for everythingthanks
On Sat, Nov 8, 2008 at 2:10 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> "Greg Hauptmann" <[EMAIL PROTECTED]> writes:
>
>> in fact I guess I was fishing for an easier way than this...if one
>> exis
"Greg Hauptmann" <[EMAIL PROTECTED]> writes:
> in fact I guess I was fishing for an easier way than this...if one
> exists? or is ruby & rspec "eql()" just strict here in terms of
> types?
>
> On 11/7/08, Mark Wilden <[EMAIL PROTECTED]> wrote:
>> On Fri, Nov 7, 2008 at 3:24 PM, Greg Hauptmann <
>
On Fri, Nov 7, 2008 at 8:53 PM, Josh Knowles <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 9:24 AM, aidy lewis <[EMAIL PROTECTED]> wrote:
>> The customer is not happy about writing Stories in a text editor.
>>
>> Has anyone else experienced this? Is anyone using a wiki, spreadsheet,
>> or wor
yep - this was recommended on forums over float - why?
On Sat, Nov 8, 2008 at 11:48 AM, Zach Dennis <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 6:24 PM, Greg Hauptmann
> <[EMAIL PROTECTED]> wrote:
>> (woops - full email below)
>>
>> Hi,
>>
>> My rails migrations / mysql database uses Decim
On Fri, Nov 7, 2008 at 9:12 PM, Greg Hauptmann
<[EMAIL PROTECTED]> wrote:
> yep - this was recommended on forums over float - why?
You are in for a lot of headaches in you application resorting to
decimal fields in the database, since it restores them as BigDecimals.
It sucks to deal with BigDecim
On Fri, Nov 7, 2008 at 9:24 AM, aidy lewis <[EMAIL PROTECTED]> wrote:
> The customer is not happy about writing Stories in a text editor.
>
> Has anyone else experienced this? Is anyone using a wiki, spreadsheet,
> or word document and automatically converting to a text file?
As Aslak mentioned th
On Fri, Nov 7, 2008 at 6:24 PM, Greg Hauptmann
<[EMAIL PROTECTED]> wrote:
> (woops - full email below)
>
> Hi,
>
> My rails migrations / mysql database uses Decimal and I've noticed in
> my rspec when I do a "...should eql(5.5)" that they're failing as the
> expected result here is a float not a de
in fact I guess I was fishing for an easier way than this...if one
exists? or is ruby & rspec "eql()" just strict here in terms of
types?
On 11/7/08, Mark Wilden <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 3:24 PM, Greg Hauptmann <
> [EMAIL PROTECTED]> wrote:
>
>>
>> expected 6.5, got
On Fri, Nov 7, 2008 at 5:17 PM, Russell Norris <[EMAIL PROTECTED]> wrote:
> Zach,
>
> Thank you so much. That works for me.
>
> I'm still confused why stubbing all calls to :bar on @foo would allow
> @foo.should_receive(:bar).with(:baz) when this doesn't work though. But I
> feel like I'm looking a
On Fri, Nov 7, 2008 at 3:51 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> "Greg Hauptmann" <[EMAIL PROTECTED]> writes:
>
> Do you mean BigDecimal? Anyway, you should probably be using == instead
> of eql.
>
> >> 5.5 == BigDecimal.new('5.5')
> => true
> >> 5.5.eql? BigDecimal.new('5.5')
> => false
>
"Greg Hauptmann" <[EMAIL PROTECTED]> writes:
Do you mean BigDecimal? Anyway, you should probably be using == instead
of eql.
>> 5.5 == BigDecimal.new('5.5')
=> true
>> 5.5.eql? BigDecimal.new('5.5')
=> false
eql? is object identity and is generally not what you're after.
Pat
__
On Fri, Nov 7, 2008 at 3:24 PM, Greg Hauptmann <
[EMAIL PROTECTED]> wrote:
>
> expected 6.5, got # (using .eql?)
>
How about just expecting BigDecimal('5.5')?
///ark
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailma
There's my C roots showing. :) That should be BigDecimal.new('5.5'), of
course.
On Fri, Nov 7, 2008 at 3:47 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 3:24 PM, Greg Hauptmann <
> [EMAIL PROTECTED]> wrote:
>
>>
>> expected 6.5, got # (using .eql?)
>>
>
> How about just
(woops - full email below)
Hi,
My rails migrations / mysql database uses Decimal and I've noticed in
my rspec when I do a "...should eql(5.5)" that they're failing as the
expected result here is a float not a decimal. For example see
extract below:
expected 6.5, got # (using .eql?)
What's
--
Sent from my mobile device
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
oh, I hadn't known there was a "rspec-rails" gem. Thanks
On 11/7/08, Fernando Perez <[EMAIL PROTECTED]> wrote:
> Greg Hauptmann wrote:
>> Hi,
>>
>> I've got the rspec gem installed, as well as the two plugins "rspec" &
>> "rspec-rails". I can't remember which is actual used and which isn't
>> fo
Zach,
Thank you so much. That works for me.
I'm still confused why stubbing all calls to :bar on @foo would allow
@foo.should_receive(:bar).with(:baz) when this doesn't work though. But I
feel like I'm looking a gift horse in the mouth here!
RSL
On Fri, Nov 7, 2008 at 4:59 PM, Zach Dennis <[EMA
Absolutely and THANKS!
Sincerely,
Tim
On Fri, Nov 7, 2008 at 1:53 AM, aslak hellesoy <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 2:02 AM, Tim Walker <[EMAIL PROTECTED]> wrote:
>> Thank you very much Aslak. That looks great. FWIW I have taught a
>> class "Executable Requirements with FitN
Per David's request i made a pastie of the whole view and the whole test of
an example of this. as well as the output. http://pastie.org/309868
RSL
On Fri, Nov 7, 2008 at 5:17 PM, Russell Norris <[EMAIL PROTECTED]>wrote:
> Zach,
>
> Thank you so much. That works for me.
>
> I'm still confused wh
On Fri, Nov 7, 2008 at 4:35 PM, Russell Norris <[EMAIL PROTECTED]> wrote:
> Can someone please explain to me why this spec fails
>
> it "should work" do
>
> template.stub!(:render)
>
> template.should_receive(:render).with(:partial => "foo")
>
> render @template_with_render_partial_foo
Can y
On Fri, Nov 7, 2008 at 4:35 PM, Russell Norris <[EMAIL PROTECTED]> wrote:
> Can someone please explain to me why this spec fails
>
> it "should work" do
>
> template.stub!(:render)
>
> template.should_receive(:render).with(:partial => "foo")
>
> render @template_with_render_partial_foo
>
> en
Can someone please explain to me why this spec fails
it "should work" do
template.stub!(:render)
template.should_receive(:render).with(:partial => "foo")
render @template_with_render_partial_foo
end
but this spec passes
it "should work" do
@foo.stub!(:bar)
@foo.should_receive(:ba
Can someone please explain to me why this spec fails
it "should work" do
template.stub!(:render)
template.should_receive(:render).with(:partial => "foo")
render @template_with_render_partial_foo
end
but this spec passes
it "should work" do
@foo.stub!(:bar)
@foo.should_receive(:bar).wit
Joseph Wilk wrote:
Ben Mabley has written a great article on imperative vs declarative
steps [2] which is a great read.
+1! That article was a real eye-opener to me.
But I keep realizing that, if you keep following the temptation to
super-abstract your specs - from scenarios into matchers,
Great news (again :D).
Ngoc.
On Sat, Nov 8, 2008 at 12:23 AM, Luis Lavena <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 12:03 PM, David Chelimsky <[EMAIL PROTECTED]>
> wrote:
> > Hey all,
> >
> > I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
> > is almost here. The
I posted a ticket to lighthouse:
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/595-deprecate-integrate_views
Please put your comments and thoughts there, as that is the best place
for that discussion. I wanted to make it more "visible" so it could
get wide community participation in c
Pat Maddox:
> "Shot (Piotr Szotkowski)" <[EMAIL PROTECTED]> writes:
>> it 'should set the debug option properly' do
>> `binary -d`
>> Conf.should_receive(:debug=).with true
>> end
> When you use backticks to execute the binary, it runs in
> a separate process, so you can't use mock expectati
David Chelimsky wrote:
On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
One technique is to have a single noisy 'declarative' scenario that
explicitly walks around filling things in, then all
On 7 Nov 2008, at 15:38, Aslak Hellesøy wrote:
Hi,
The customer is not happy about writing Stories in a text editor.
Has anyone else experienced this? Is anyone using a wiki,
spreadsheet,
or word document and automatically converting to a text file?
There will be custom editors/wikis with
Ben Mabey wrote:
Matt Wynne wrote:
Are you pairing with them? Can you not just drive and do the typing,
asking them questions all the while to keep them engaged?
I think David is cooking something up (have a look at his blog) but
it might be a while coming.
If you can find a Mac, the TextMa
"Andrew Premdas" <[EMAIL PROTECTED]> writes:
> I'm working on writing features for a wizard. The wizard collects information
> from a number of different forms, and you can navigate through
> it in a number of ways. Anyhow one of these forms is a customer form
> collecting name, and email.
>
> I
"Shot (Piotr Szotkowski)" <[EMAIL PROTECTED]> writes:
> I’m trying to spec a ‘binary’, and as previously discussed on this list,
> I’m trying to do it ‘from outside’ – i.e., by calling it with Kernel#`
> and observing the (side-)effects.
>
> Unfortunately, this doesn’t really let me spec expectati
+1 for abstract and concrete as it gives an indication of what the
story should contain i.e.
I should get an error
vs
I should be told my email must have an @ sign and be ...
Andrew
2008/11/7 David Chelimsky <[EMAIL PROTECTED]>:
> On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky <[EMAIL PROTE
You could try the bundle in the E editor on windows http://www.e-texteditor.com/
2008/11/7 aidy lewis <[EMAIL PROTECTED]>:
> Hi Matt,
>
> How are you?
>
> On 07/11/2008, Matt Wynne <[EMAIL PROTECTED]> wrote:
>> Are you pairing with them? Can you not just drive and do the typing, asking
>> them que
Hi,
The customer is not happy about writing Stories in a text editor.
Has anyone else experienced this? Is anyone using a wiki, spreadsheet,
or word document and automatically converting to a text file?
There will be custom editors/wikis with aides like code completion,
nice visuals, run
Matt,
Thanks for reply much appreciated and very helpful
I'm definitely feeling a need/desire to write features at different
levels as you say, and in this case I am trying both, though I haven't
quite worked out a nice way of organising things as yet. I definitely
want to seperate my 'noisy' fro
Joseph,
Thanks for your reply, much appreciated.
The scenarios don't have titles just for this discussion. Felt including
them would be a distraction.
I agree that some of the Givens should be Whens in these examples e.g.
Given I step to customer
When I fill in my customer details incorrect
On 7 Nov 2008, at 14:42, aidy lewis wrote:
On 07/11/2008, Matt Wynne <[EMAIL PROTECTED]> wrote:
Are you pairing with them? Can you not just drive and do the
typing, asking
them questions all the while to keep them engaged?
Cucumber is now the standard here, with all projects using it. The
gu
David Chelimsky wrote:
On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
One technique is to have a single noisy 'declarative' scenario that
explicitly walks around filling things in, then all
On 7 Nov 2008, at 15:02, David Chelimsky wrote:
On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky
<[EMAIL PROTECTED]> wrote:
On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <[EMAIL PROTECTED]>
wrote:
One technique is to have a single noisy 'declarative' scenario that
explicitly walks around filling
Matt Wynne wrote:
Are you pairing with them? Can you not just drive and do the typing,
asking them questions all the while to keep them engaged?
I think David is cooking something up (have a look at his blog) but it
might be a while coming.
If you can find a Mac, the TextMate text editor has
Hey all,
I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
is almost here. The plan is:
* beta/pdf in December, 2008
* print in April, 2009
The RSpec Book, authored by me, Dave Astels, Zach Dennis, Aslak
Hellesøy, Bryan Helmkamp, and Dan North, will comprise material on
RSpec
On Fri, Nov 7, 2008 at 12:03 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> I'm pleased to announce that the Pragmatic Bookshelf's The RSpec Book
> is almost here. The plan is:
>
> * beta/pdf in December, 2008
> * print in April, 2009
>
> The RSpec Book, authored by me, Dave Astels,
On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
>> One technique is to have a single noisy 'declarative' scenario that
>> explicitly walks around filling things in, then all the rest use more
>> 'impe
Hi Matt,
How are you?
On 07/11/2008, Matt Wynne <[EMAIL PROTECTED]> wrote:
> Are you pairing with them? Can you not just drive and do the typing, asking
> them questions all the while to keep them engaged?
Cucumber is now the standard here, with all projects using it. The
guys who were using Wat
As Matt said there is no specalised tool for editing Features (Though
textmate is great with Bens bundle).
If you checkout Cucumbers Milestone 0.2 you will notice ' Provide a
REST/AtomPub interface to Cucumber'. The idea of having some sort of
wiki interface is something thats in the works for C
On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> One technique is to have a single noisy 'declarative' scenario that
> explicitly walks around filling things in, then all the rest use more
> 'imperative' style steps where most of the detail is buried away.
You've got those b
On 7 Nov 2008, at 06:09, Andrew Premdas wrote:
I'm working on writing features for a wizard. The wizard collects
information from a number of different forms, and you can navigate
through it in a number of ways. Anyhow one of these forms is a
customer form collecting name, and email.
In th
Are you pairing with them? Can you not just drive and do the typing,
asking them questions all the while to keep them engaged?
I think David is cooking something up (have a look at his blog) but it
might be a while coming.
If you can find a Mac, the TextMate text editor has nice syntax
hi
Hi,
The customer is not happy about writing Stories in a text editor.
Has anyone else experienced this? Is anyone using a wiki, spreadsheet,
or word document and automatically converting to a text file?
Thanks
Aidy
___
rspec-users mailing list
rspec-u
I’m trying to spec a ‘binary’, and as previously discussed on this list,
I’m trying to do it ‘from outside’ – i.e., by calling it with Kernel#`
and observing the (side-)effects.
Unfortunately, this doesn’t really let me spec expectations about its
internals. Let’s assume I have a -d flag and I par
> forgot to clarify - for rails development you'll need both rspec and
> rspec-rails.
What I meant is that you can go plugin-less, you just have to install
the two following gems: rspec and rspec-rails, then bootstrap your app
by generating a few files. And your set.
I personally prefer using g
On Fri, Nov 7, 2008 at 12:56 PM, aslak hellesoy
<[EMAIL PROTECTED]> wrote:
> On Fri, Nov 7, 2008 at 11:23 AM, Greg Hauptmann
> <[EMAIL PROTECTED]> wrote:
>> so just to be clear are you saying:
>>
>> * rspec gem => All that is need for Ruby on Rails Rspec work
>> * 'rspec plugin' => not needed (func
On Fri, Nov 7, 2008 at 11:23 AM, Greg Hauptmann
<[EMAIL PROTECTED]> wrote:
> so just to be clear are you saying:
>
> * rspec gem => All that is need for Ruby on Rails Rspec work
> * 'rspec plugin' => not needed (functionality in gem)
> * 'rspec-rails' plugin => not needed (functionality in gem)
>
>
Andrew Premdas wrote:
I'm working on writing features for a wizard. The wizard collects
information from a number of different forms, and you can navigate
through it in a number of ways. Anyhow one of these forms is a
customer form collecting name, and email.
In the context of the wizard I fe
so just to be clear are you saying:
* rspec gem => All that is need for Ruby on Rails Rspec work
* 'rspec plugin' => not needed (functionality in gem)
* 'rspec-rails' plugin => not needed (functionality in gem)
is this right?
thanks again
On Fri, Nov 7, 2008 at 8:10 PM, Fernando Perez <[EMAIL P
Greg Hauptmann wrote:
> Hi,
>
> I've got the rspec gem installed, as well as the two plugins "rspec" &
> "rspec-rails". I can't remember which is actual used and which isn't
> for my rails app when I go "rake spec"? Anyone know?
>
> Could I remove either of the core rpec gem OR the "rspec plugi
On Fri, Nov 7, 2008 at 2:02 AM, Tim Walker <[EMAIL PROTECTED]> wrote:
> Thank you very much Aslak. That looks great. FWIW I have taught a
> class "Executable Requirements with FitNesse" as the director of
> training and coaching at Valtech and on the faculty of agile
> university. I went back to a
Hi,
I've got the rspec gem installed, as well as the two plugins "rspec" &
"rspec-rails". I can't remember which is actual used and which isn't
for my rails app when I go "rake spec"? Anyone know?
Could I remove either of the core rpec gem OR the "rspec plugin"? or
do I need all three componen
62 matches
Mail list logo
