Any fix on this yet?
On Sat, Aug 9, 2008 at 8:33 AM, Jd Roberts <[EMAIL PROTECTED]> wrote:
> > Are you running under drb? Autotest? What version of rspec? rails?
> >
> > I'm almost certain this is a rails loading bug...Are you requiring
> > anywhere? What is the value of config.cache_classes
Every time I save a model spec I get this:
super: no superclass method `respond_to?'
And I have to restart autotest to get it to go away.
Is there any solution to this?
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman
Yea a fix would be amazing. This is knda annoying because now I have to
press ctrl-c or something to run that spec.
On Sun, Apr 6, 2008 at 12:36 PM, Willem Källman <[EMAIL PROTECTED]>
wrote:
> Same problem here, but I guess it has nothing to do with RSpec or the
> fact that you are testing a mode
If I save my model while autotest is running, autotest doesn't run the
model's specs, all I get in my window is
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -S
script/spec -O spec/spec.opts
However if I go to the spec and save that, it'll automatically run that
spec... it j
(User, :writings => [] )
I'm not sure if that is a bug or what, but that's what caused it.
It'd also say "no block given" if I put something there other than a "mock".
On Dec 3, 2007 10:33 PM, Fischer, Daniel <[EMAIL PROTECTED]> wrote:
> Alright, tha
bave0ph2mkcgp6w
On Dec 3, 2007 9:33 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Dec 3, 2007 10:26 PM, Fischer, Daniel <[EMAIL PROTECTED]> wrote:
> > Hey cool, thanks for the help guys. One problem though, when I take this
> > approach I can't decouple the sp
ngs.find(params[:id])
respond_to do |format|
format.html
format.xml { render :xml => @writing.to_xml }
end
end
http://pastie.textmate.org/private/99vq9ipqb6u8cu5bfirlaa here is the
pastie.
On Dec 3, 2007 8:26 PM, Fischer, Daniel <[EMAIL PROTECTED]> wrote:
> Hey
;
> > class User do
> >
> > def find_articles_for_user
> >Article.find(:all, :conditions => ['userid = ?', id)
> > end
> >
> > end
> >
> > Then you'd use a mock in your controller spec, and make sure you test
>
other hand, the user model should be tested directly against the
> db.
>
> HTH,
>
> Stefan
>
> 2007/12/3, Fischer, Daniel <[EMAIL PROTECTED]>:
> >
> > Let's say you're using the restful_authentication plugin.
> > You have a model called articles.
Let's say you're using the restful_authentication plugin.
You have a model called articles. On the index action of the
articlescontroller you simply want to spec out that it'll scope the results
to the ownership of the current_user.
It should NOT include any articles other than the articles that u
Let's say you're using the restful_authentication plugin.
You have a model called articles. On the index action of the
articlescontroller you simply want to spec out that it'll scope the results
to the ownership of the current_user.
It should NOT include any articles other than the articles that u
Okay, I've never "selected" a bundle before. Shouldn't the bundle
automatically parse the document to see if it matches that bundle? for
e.ghaving "spec" in the file name? What extra steps am I missing?
On 9/11/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
So is it just me, or is the new rspec bundle not working as intended when
using the "run" shortcuts?
shift + cmd + r doesn't work. (brings up ruby execution)
cmd + r doesn't work. (brings up ruby execution)
and option + cmd + r brings up a filter dialog
They do work if I select it manually throug
Please let us know when it's updated :)
On 9/10/07, Bryan Liles <[EMAIL PROTECTED]> wrote:
>
>
> On Sep 8, 2007, at 5:59 PM, David Chelimsky wrote:
>
> > Hi all, I got some help from James Edward Gray II on the RSpec
> > TextMate bundle. For those of you who don't know James, he runs the
> > Ruby
It's redirecting to /users/1 so it's not causing a fail on the exception,
which I don't know why. My question is how to properly do this in rSpec?
On 8/8/07, Lance Carlson <[EMAIL PROTECTED]> wrote:
>
> Does it redirect instead?
>
> On 8/8/07, Fischer, Daniel
1 def create
2 @user = User.new(params[:user])
3 @user.save!
4 self.current_user = @user
5 redirect_to user_path(@user)
6 flash[:notice] = "Thanks for signing up!"
7 rescue ActiveRecord::RecordInvalid
8 render :action => 'new'
9 end
I can't seem to properly s
Hello,
I'm trying to figure out how to setup a spec structure for plugins. I'm
getting pretty lost in figuring out how to isolate a plugin enviornment
emulating rails, but not actually being reflected upon the current rails
project.
What I mean is this, let's say I have a comment plugin. This has
My problem:
Mock 'Task_1005' received unexpected message :user_id= with (1)
No matter what I do to try to stub that out it will still fail out and give
me that message.
Here is my spec
describe TasksController, "handling POST /tasks" do
before(:each) do
@task = mock_model(Task, :to_param
18 matches
Mail list logo
