When i run a spec file i am getting the following error
D:\Diwakar\spec_diwa\spec\controllers>spec sandbox_controller_spec.rb
c:/ruby/lib/ruby/gems/1.8/gems/rspec-0.5.15/lib/spec/api/sugar.rb:17:in
`method_
missing': undefined method `describe' for main:Object (NoMethodError)
from ./sa
On Fri, Oct 10, 2008 at 1:17 AM, Dennis Sutch <[EMAIL PROTECTED]> wrote:
> Hello,
> I have noticed that, since version 1.1.4, autotest/autospec does not run any
> of my specs. After getting a hint
> from http://b.logi.cx/2008/10/9/non-auto-spec, I dove a bit deeper into the
> code and found that s
Hello,
I have noticed that, since version 1.1.4, autotest/autospec does not run any
of my specs. After getting a hint from
http://b.logi.cx/2008/10/9/non-auto-spec, I dove a bit deeper into the code
and found that spec is no longer being run by ruby.
I monkey-patched Autotest::Rspec in my .autot
Ahh, one of the cool things about Ruby compared to the C family of languages
comes back to bite me. :)
///ark
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Thu, Oct 9, 2008 at 6:47 PM, Mark Wilden <[EMAIL PROTECTED]> wrote:
> I expected 'should !=' to act the same as 'should_not =='. That turned out
> to be incorrect (by design?):
We'd love to do that, but Ruby doesn't provide us the tools we need.
As far as we know, the only way to do that would
"Mark Wilden" <[EMAIL PROTECTED]> writes:
> I expected 'should !=' to act the same as 'should_not =='. That turned out to
> be incorrect (by design?):
>
> require 'spec'
> require 'spec/rails'
>
> describe "using 'should !='" do
> it "seems to treat != as the same as ==" do
> 1.should != 1
I expected 'should !=' to act the same as 'should_not =='. That turned out
to be incorrect (by design?):
require 'spec'
require 'spec/rails'
describe "using 'should !='" do
it "seems to treat != as the same as ==" do
1.should != 1 # passes
1.should != 2 # fails
end
end
___
Pat Maddox wrote:
I've written [1] about using shared example groups to do this sort of
things. You're already using them :) but maybe you can still get
something out of that post.
What specifically don't you like about this solution?
What Matt proposed is very nice. :) I was struggling with
On 2008-10-08, at 07:01, Jeroen van Dijk wrote:
Hi all,
I'm new to this list and new to RSpec so I have been trying out
RSpec the last couple of days and I find it very a natural way of
testing. So first of all thanks for providing this framework.
Now, I have written some tests for my cont
I have a controller test, where I want to do a GET on a page. Our URL's are
complex, and need to be correct (duh, but we allow some slop, but that
causes a redirect which I want to avoid). Anyway, in my controller test I
do a get to the URL that is produced by a helper method which calls a named
I've written [1] about using shared example groups to do this sort of
things. You're already using them :) but maybe you can still get
something out of that post.
What specifically don't you like about this solution?
Pat
[1] http://evang.eli.st/blog/2008/5/14/refactoring-with-shared-example-gr
David Chelimsky wrote:
Not sure why what you're doing works at all
Oh oops, I forgot to mention that I also have 'shared_examples_for
"AbstractServer-like" behavior'.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailma
On 9 Oct 2008, at 18:20, Hongli Lai wrote:
I currently have a base class and 2 subclasses. I'm struggling with
finding the best way to test them. This is the current situation.
What's the best way to solve this? What are good practices for
testing inherited behavior? Should I be testing my ch
Thanks guys. I took your advice and moved to cucumber. It did turn out
to be useful in that the more verbose error reporting led me to dive
more deeply into the webrat source, eventually leading me to my problem
- which actually was essentially the same noob error I made a few days
when I faile
On Thu, Oct 9, 2008 at 12:20 PM, Hongli Lai <[EMAIL PROTECTED]> wrote:
> I currently have a base class and 2 subclasses. I'm struggling with finding
> the best way to test them. This is the current situation.
>
> The base class is called AbstractServer. It's not really abstract because it
> can be
Before I dive into the code and fix it, has anyone else worked around
/ found the solution to calling 'clicks_button' when the button is
actually a button and not an input?
ie:
Text... / Image here
Calling clicks on this doesn't find it as webrat only looks for
input[type=submit].
Mikel
I currently have a base class and 2 subclasses. I'm struggling with
finding the best way to test them. This is the current situation.
The base class is called AbstractServer. It's not really abstract
because it can be instantiated and used, but some important methods are
defined as no-ops, and
Scott Taylor <[EMAIL PROTECTED]> writes:
> I find it sort of interesting that they are using RSpec in one of the
> courses @ UC Berkley:
>
> http://radlab.cs.berkeley.edu/wiki/Cs198
>
> Scott
I'd like to study at Berkeley. I wonder if this would help me get in?
Pat
_
Pat Maddox wrote:
> Daniel Higginbotham <[EMAIL PROTECTED]> writes:
>
>>> ActiveRecord::Schema.verbose = false
>>> { :name => "blah", :id => 1 },
>>
>> end
>> end
>>
>> Are you similarly able to load your YAML fixtures from spec/fixtures
>> when you're running a Cucumber feature?
>>
>> T
Hello,
i written a rails plugin for driving Selenium from
the RSpec Story Runner:
http://github.com/tmak/rspec-rails-selenium-story
Now, i want to migrate my plugin to cucumber.
My question:
I used the scenario_failed method of the Story Listener to make
screenshots of failing story scenari
On Thu, Oct 9, 2008 at 1:57 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> On 9 Oct 2008, at 02:55, Mark Thomson wrote:
>
>> I have an RSpec story with an overall structure that looks something like
>> this -
>>
>>
>> Given the user is on the start page
>> When the user clicks the 'new' button
>>
On Thu, Oct 9, 2008 at 4:40 AM, Guofeng Ma <[EMAIL PROTECTED]> wrote:
>
> I use rspec_scaffold to generate a part of examples as below:
>
> it "should expose a newly created awarding_body as @awarding_body" do
>AwardingBody.should_receive(:new).with({'these' =>
> 'params'}).and_return(mock_
On Thu, Oct 9, 2008 at 2:21 AM, Scott Taylor
<[EMAIL PROTECTED]> wrote:
>
> I find it sort of interesting that they are using RSpec in one of the
> courses @ UC Berkley:
>
> http://radlab.cs.berkeley.edu/wiki/Cs198
Ah - but look at the install instructions. They're using svn at
rubyforge :( That's
On Thu, Oct 9, 2008 at 2:04 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> On 9 Oct 2008, at 01:18, David Chelimsky wrote:
>>>
>>> Now since I upgraded my gem to rspec 1.8 today, the empty example is
>>> failing
>>> with the error ArgumentError in "should do something someday": block not
>>> supplied
I use rspec_scaffold to generate a part of examples as below:
it "should expose a newly created awarding_body as @awarding_body" do
AwardingBody.should_receive(:new).with({'these' =>
'params'}).and_return(mock_awarding_body(:save => true))
post :create, :awarding_body => {:these =
I find it sort of interesting that they are using RSpec in one of the
courses @ UC Berkley:
http://radlab.cs.berkeley.edu/wiki/Cs198
Scott
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On 9 Oct 2008, at 01:18, David Chelimsky wrote:
Now since I upgraded my gem to rspec 1.8 today, the empty example
is failing
with the error ArgumentError in "should do something someday":
block not
supplied
Is this by design?
Absolutely not, though I am not having the same experience (bloc
27 matches
Mail list logo
