On Tue, Apr 14, 2009 at 8:24 AM, Salil Gaikwad wrote:
> following is the method of the helper
>
> module ApplicationHelper
> def tab_class(tab)
>'class="active"' if tab == params[:controller]
> end
> end
>
> i write the spec method as follows
>
> describe ApplicationHelper do
> it "should
following is the method of the helper
module ApplicationHelper
def tab_class(tab)
'class="active"' if tab == params[:controller]
end
end
i write the spec method as follows
describe ApplicationHelper do
it "should be active if controller is same" do
tab_class('royalty_statement').s
On Tue, Apr 14, 2009 at 6:06 AM, Korny Sietsma wrote:
> In case anyone followed this: I got everything working pretty nicely - now
> I have a cucumber formatter that automatically updates a confluence wiki.
>
> I still have to cover some bits like table outputs and the like, but the
> basics are
In case anyone followed this: I got everything working pretty nicely - now I
have a cucumber formatter that automatically updates a confluence wiki.
I still have to cover some bits like table outputs and the like, but the
basics are pretty nice - I use cucumber to parse the features and create a
w
On Mon, Apr 13, 2009 at 7:46 AM, aslak hellesoy
wrote:
>
> So if someone develops a better AutoTest with a plugin architecture, and
> that doesn't have to run as a long/lived process, then I'd be very
> interested in writing the neural network part - possibly backed by FANN
> (http://leenissen.dk/
Hi Folks,
I want to assert on an order of interaction between two objects where one
method gets repeated.
Here is a simple example...
# this fails "Mock 'x' expected :a with (any args) once, but received it twice"
x = mock("x")
x.should_receive(:a).once.ordered
x.should_receive(:b).once.ordered
Hi Folks,
I want to assert on an order of interaction between two objects where one
method gets repeated.
Here is a simple example...
# this fails "Mock 'x' expected :a with (any args) once, but received it twice"
x = mock("x")
x.should_receive(:a).once.ordered
x.should_receive(:b).once.ordered
On Mon, Apr 13, 2009 at 4:46 PM, Sarah Gray wrote:
> Jeff, always a good idea -- it didn't work in this case, but I've seen it
> before. I ended up uninstalling my rails gem (and the action* gems) and
> reinstalling; then, reinstalling rspec and rspec-rails. After that, rspec
> worked without t
On Tue, Apr 14, 2009 at 12:08 AM, John Goodsen wrote:
> OK, I'll reproduce in a simple example and create a ticket...
>
>
Excellent - I'll get to it ASAP
>
> On Sat, Apr 11, 2009 at 3:56 AM, aslak hellesoy
> wrote:
>
>>
>>
>> On Fri, Apr 10, 2009 at 5:29 PM, John Goodsen wrote:
>>
>>> so I'm s
OK, I'll reproduce in a simple example and create a ticket...
On Sat, Apr 11, 2009 at 3:56 AM, aslak hellesoy wrote:
>
>
> On Fri, Apr 10, 2009 at 5:29 PM, John Goodsen wrote:
>
>> so I'm still stumped... how do I tell keep cucumber from loading the
>> *SAME* steps more than once when I run multi
On Mon, Apr 13, 2009 at 10:09 PM, Matt Wynne wrote:
>
> On 13 Apr 2009, at 12:46, aslak hellesoy wrote:
>
> A couple of years ago I was on a project that had fallen into the trap of
>> too many integration tests (exactly the horror scenario that J.B.
>> Rainsberger describes: http://www.jbrains.
I am moving into yet another area that I possess absolutely no
experience with. In this case the realm of RSS feeds and Rails as the
consumer.
My first feature/scenario looks like this and, given the effort I had to
make to grasp the basics of features and scenarios in the crud world, I
thought it
Jeff, always a good idea -- it didn't work in this case, but I've seen it
before. I ended up uninstalling my rails gem (and the action* gems) and
reinstalling; then, reinstalling rspec and rspec-rails. After that, rspec
worked without the issues I'd seen before. Don't know why.
Thanks.
On Mon,
I'm sure you have tried this, but it's such a simple step that I'll throw it
out.
I've had a couple instances in the past where gems were not being loaded and
after troubleshooting for a while, I found that all problems were magically
solved by firing up a new instance of my shell (new terminal wi
On Mon, Apr 13, 2009 at 5:04 PM, Sarah Gray wrote:
> When uninstalling rspec, should you:
> Remove executables:
> autospec, spec
> in addition to the gem? [Yn]
> And, is there possible fallout from doing this step wrong?
As long as you're going to reinstall it, then there should not be any fallou
On 13 Apr 2009, at 12:46, aslak hellesoy wrote:
A couple of years ago I was on a project that had fallen into the
trap of too many integration tests (exactly the horror scenario that
J.B. Rainsberger describes: http://www.jbrains.ca/permalink/239).
The whole suite had hundreds of slow wati
On 12 Apr 2009, at 23:51, Ben Mabey wrote:
Stephen Eley wrote:
On Sat, Apr 11, 2009 at 2:02 PM, Ashley Moran
wrote:
I was just idly thinking, could a code-coverage based system could
be
combined with some sort of failure (fragility) history to balance
the time
cost of heavy feature runs
When uninstalling rspec, should you:
Remove executables:
autospec, spec
in addition to the gem? [Yn]
And, is there possible fallout from doing this step wrong?
On Mon, Apr 13, 2009 at 2:48 PM, David Chelimsky wrote:
> On Mon, Apr 13, 2009 at 4:34 PM, Sarah Gray wrote:
> > rails -v
> > 2.3.2
On Mon, Apr 13, 2009 at 4:34 PM, Sarah Gray wrote:
> rails -v
> 2.3.2
Me too. Not sure what to tell you.
Anybody else?
> (Sorry about that long stack trace in the last message!)
>
> On Mon, Apr 13, 2009 at 2:29 PM, David Chelimsky
> wrote:
>>
>> On Mon, Apr 13, 2009 at 3:36 PM, Sarah Gray wro
On 11 Apr 2009, at 19:02, Ashley Moran wrote:
I was just idly thinking, could a code-coverage based system could
be combined with some sort of failure (fragility) history to balance
the time cost of heavy feature runs with the benefits of having
something run end-to-end? We've had reverse
You could look at fbrp (http://github.com/diabolo/fbrp/tree/master) which
has lots of tests like this.
You could add a debug statement when you visit a page that you actually have
to be logged in, to see if you actually are logged in.
I suspect of the top of my head that you are not logged in when
On Mon, Apr 13, 2009 at 3:36 PM, Sarah Gray wrote:
> David, thanks, that does appear to be true, which is helpful to know,
> thanks. But the "gem which" problem was really the canary in the coal mine
> for the fact that the gems aren't being recognized when I am attempting to
> configure them:
> $
On Mon, Apr 13, 2009 at 2:22 PM, Sarah Gray wrote:
> Hello RSpec-list:
> I'm having trouble getting rspec and rspec-rails correctly installed on my
> system. (I had to uninstall, unfortunately).The upshot is that even when
> they are installed -- i.e. when I can see them on my system -- they don't
Hello RSpec-list:
I'm having trouble getting rspec and rspec-rails correctly installed on my
system. (I had to uninstall, unfortunately).The upshot is that even when
they are installed -- i.e. when I can see them on my system -- they don't
appear known to gem which which and, more importantly, the
>> A quick fix is to install rspec and rspec-rails gems on production
>> server, but I don't get why the app wants them installed.
>
> This is a tricky business.
>
> We put that in there in response to a user who works on a team. One
> team member had pulled code and tried t run specs and got an
Kero van Gelder wrote:
That would be very cool, you have lots of good ideas there. Being able
to plug in your own file-change strategy would be killer. Another cool
idea I ran across the other idea is being able to specify in your
examples that which ones are "focussed". Meaning, autotest
On Mon, Apr 13, 2009 at 8:17 AM, David Chelimsky wrote:
> On Mon, Apr 13, 2009 at 12:09 PM, Salil Gaikwad wrote:
>> How to write a spec file for a following helper
>>
>> module ArtistsHelper
>>
>> def round_to(x)
>> (self * 10**x).round.to_f / 10**x
>> end
>>
>> end
>
> in spec/helpers/artists
David Chelimsky wrote:
On Mon, Apr 13, 2009 at 12:06 PM, Salil Gaikwad wrote:
how to write a spec for an actionmailer method.
Check out http://github.com/bmabey/email-spec/
Cheers,
David
Specifically, look at this example for an idea on how to use it with RSpec:
http://github.c
On Mon, Apr 13, 2009 at 12:09 PM, Salil Gaikwad wrote:
> How to write a spec file for a following helper
>
> module ArtistsHelper
>
> def round_to(x)
> (self * 10**x).round.to_f / 10**x
> end
>
> end
in spec/helpers/artists_helper_spec.rb:
describe AristsHelper do
it "rounds to " do
On Mon, Apr 13, 2009 at 12:06 PM, Salil Gaikwad wrote:
> how to write a spec for an actionmailer method.
Check out http://github.com/bmabey/email-spec/
Cheers,
David
>
> following is the method of action controller.
>
> class Notifier < ActionMailer::Base
>
> def conta(username ,adresseemail,c
How to write a spec file for a following helper
module ArtistsHelper
def round_to(x)
(self * 10**x).round.to_f / 10**x
end
end
Regards
salil
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://
how to write a spec for an actionmailer method.
following is the method of action controller.
class Notifier < ActionMailer::Base
def conta(username ,adresseemail,code)
@subject = 'Admin Confirmation Mail'
@recipients = adresseemail
@body["Username"]= username
@body["adressee
On Sun, Apr 12, 2009 at 6:47 AM, Stephen Eley wrote:
> On Sat, Apr 11, 2009 at 2:02 PM, Ashley Moran
> wrote:
> >
> > I was just idly thinking, could a code-coverage based system could be
> > combined with some sort of failure (fragility) history to balance the
> time
> > cost of heavy feature r
On Mon, Apr 13, 2009 at 4:19 AM, Brandon Olivares
wrote:
> Hi,
>
> I've noticed in several matchers that the matcher method passes self to the
> constructor of the class. Then that's used to call several of the methods
> used. For instance, in RouteFor, self is passed, and it is used to call
> ass
> That would be very cool, you have lots of good ideas there. Being able
> to plug in your own file-change strategy would be killer. Another cool
> idea I ran across the other idea is being able to specify in your
> examples that which ones are "focussed". Meaning, autotest will only
> r
Hi,
I've noticed in several matchers that the matcher method passes self to the
constructor of the class. Then that's used to call several of the methods
used. For instance, in RouteFor, self is passed, and it is used to call
assert_recognizes.
I'm just curious why this is, and when this is requi
36 matches
Mail list logo
