search for: langenberg

I''m doing a redirect in one of my controller actions and somehow I can''t spec it, see this pastie: http://pastie.caboo.se/53120. When following the link from a browser I''m being redirected to the right page. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...for this GAM, I am confused because of this part in the model: *s(day,by=mapID). *I have been reading through the GAM, an introduction with R book from Wood, S. but could not find anything about predictions with BY in the model. I hope someone can help me out with this, Sincerely yours, Robbert Langenberg [[alternative HTML version deleted]]

I wanted to use ARTS to add RJS in a behaviour driven way to my application, but I''m having some trouble asserting a replace_html with a partial. I''ve created a pastie (http://pastie.caboo.se/60694) which contains the RJS I want to spec, the spec which I already wrote and its failure message. I''m currently using RSpec-0.9.2

...olkit and we only want to specify the behaviour of the code we write self, we must plug a framework somewhere, to capture the actual calls to this toolkit to know if our code is doing the right thing. At least, that''s how I see it currently. But how could that be done? Regards, Matthijs Langenberg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20071117/412ed0e7/attachment.html

Why can''t I use the RESTful route helpers in my specs? In my controller I''m doing a redirect: redirect_to list_path(:id => @item.list_id) Now when I write: controller.should_redirect_to list_path(:id => 2) I''m getting the following error: NoMethodError in ''POST on /lists/2/items should redirect to index on succesful POST'' You have a nil object

Behind every great release is a maintenance release. Go get it while it''s hot. We''ve also reworked the website a little - trying to scare off fewer people. Aslak

Hello! I''m pretty new to unit testing, and have only been using RSpec for a few weeks. I found that for my controller specs, my setup methods were getting very long building mocks/stubs for all the model objects I needed to work with. I''ve started creating helpers like the following for each of my models. The "min_" methods are short for "minimum", and

Would it be desirable to have before and after take a spec name as well as :each and :all? Scott

I really would like to know how people are using the Story and Example runner to write their software.It would be great to get some direction on it, because I think I''m missing some points. Taking the outside-in approach in thought: At first we write a high-level customer-facing story, this story fails. Then we start using mocks at object level to use them as a design tool, and so we

Many posts on this list are about using RSpec with Rails and that''s the way I''m also using RSpec all the time. Unfortunately there isn''t that much info about using RSpec for standalone Ruby projects. I must admit I''m really having a hard time writing the very first example(s) for a fresh standalone Ruby project. I haven''t really got a clue where to

Hi, I''m new to rspec and wanted to translate some of my unit tests into rspecs. Unfortunately my first test fails with "Mysql not loaded". My application is running fine and can access the database. I''d appreciate any help, so I can get started. Tino -------------- next part -------------- An HTML attachment was scrubbed... URL:

...does a SOAP request to a .NET webservice, returning me all customers straight from a MS Dynamics database. I haven''t written any code yet, but I was wondering if there is anyone already busy with such a project or willing to help me get something from the ground. Best regards, Matthijs Langenberg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send...

Announcing... JobsOnRails! I''m creating on a Ruby on Rails oriented job site and will be launching in the next few weeks. It''s a Rails-centric place for developers and employers to get in touch with a minimum of hassle. For now, I have a short outline of my ideas and an email signup form on the live site at http://www.jobsonrails.com. The site is coming along nicely and

Hi all ! I just started writing specs on a new project. I would just like to validate that this is the way you would write it. I know about mocks, stubs and expectations. I don''t think this is a problem for me. My question really boils down to: def index @projects = current_user.projects.active end My spec needs to return the proxy, no ? Here''s my code: context "A

Not sure if this is possible currently. I have a section of code like this: ActiveRecord::Base.transaction do cow.save! duck.save! dog.save! end (Names changed to protect the innocent.) I''d like to specify that the saves run in a transaction. I can do ActiveRecord::Base.should_receive(:transaction).and_yield But is there any way to specify that the code is

Hi all, I'm using SAMBA with LDAP as my PDC but after I join a workstations Windows XP to the domain, I can't authenticate any user with this workstation, It gives the fallowing error when I press ctrl+alt+del and try to logon: "The system can't authenticate the user. Check if the user and password is correct then retype them press ok" etc..... In the server, I can see the

I''m trying to write specs for a plugin I''m developing named audit_fu, and I''m running into a problem which I can''t get past it. I''ve got the same specs setup in the main rails app, and everything works fine there, it''s just running the plugin specs that I''m having a problem with. My setup is: - edge rails - edge rspec (in

I tend to write a fresh description block for every change in the parameters for that specific action, because I hate conditionals in the example describtion, e.g.: describe SomeController, "handling GET /path/with/param/3" do it "should do this" it "should not do this if" it "should still do that in both cases" end Seperate description blocks keep