similar to: Deferred success for specs?

I haven’t found a complete big-picture walkthrough for the Rails startup process when I looked for one recently. There are some really useful resources about this but they are for Rails 1.2 and each of them only covers certain parts of the process. Thus, I’ve taken some notes while reading to the Rails code and compiled the following guide from them.

I find myself doing this kind of thing a lot in Controller Specs: @vacancy = mock_model(Vacancy) @vacancy.stub!(:reference) @vacancy.stub!(:title) @vacancy.stub!(:created_at) @vacancy.stub!(:updated_at) @vacancy.stub!(:body) @vacancy.stub!(:contract) @vacancy.stub!(:location) @vacancy.stub!(:salary) @vacancy.stub!(:benefits)

Hi Evgeniy, So, to XFAIL some UBSAN failues, I found an issue: UndefinedBehaviorSanitizer-AddressSanitizer :: TestCases/TypeCheck/vptr.cpp UndefinedBehaviorSanitizer-Standalone :: TestCases/Misc/missing_return.cpp These two tests fail on that configuration, but pass when reversed. So, if I XFAIL: armv7l..., I get the following error: UndefinedBehaviorSanitizer-AddressSanitizer ::

Hello, Just decided to check whether I am doing something that makes sense or not. I was thinking about how cool would it be to re-use examples (just like we reuse story scenarios with GivenScenario). I was not sure if this possibility already exists in rspec (and, honestly, was lazy to check), so I have created this helper: def given_it(name) example_definition =

Hey, May be it is just too deep night over here and I''m missing something though I got this failure on {{{response.should_not redirect_to}}}: ''QueuesController should allow authenticated user to access ''show'''' FAILED Matcher does not support should_not. See Spec::Matchers for more information about matchers. Also I''ve found this in

Now that RSpec is nearing 1 dot oh, are there any plans to implement an integration testing equivalent in RSpec On Rails?

I want to create a spec/regressions directory with various regressions (for my rails project). I tried the following: describe LoginController, "regression for user creation when steves_sister does not exist", :behavior_type => :controller do controller_name :login before :each do @params = { "commit"=>"Create Account",

My thoughts: On Sat, Dec 1, 2012 at 9:06 AM, Chandler Carruth <chandlerc at google.com>wrote: > On Fri, Nov 30, 2012 at 8:04 PM, Chris Lattner <clattner at apple.com>wrote: > >> I'm ok with this in principle, but how about with the nuance that some >> tests (eg test/codegen) explicitly opt into march=native? >> > > I'd really like the default

Trying to figure out the best way to pull an active call out of a queue by unique id and put it on hold. I don't want to put it on hold on the agent's phone but I want it to be pulled away from the agent's phone and into Asterisk limbo somewhere. Shortly after I want to pull the same call out of limbo and redirect it back to either the same agent or another. I was thinking about call

Hi folks. Is use Linux Mageia 2 Cauldron x86_64 and I install with repository wine. In system I have Code: wine64-1.3.25-2.mga2 wine64-gecko-1.2.0-1.mga1 wine32-1.3.25-2.mga2 lib64kwineffects1-4.7.0-3.mga2 wine-gecko-1.2.0-1.mga1 I installed 64-bit version because many applications ie Winrar 64bit I did not work. But now there are problems to me, I have a game Limbo

<dynarray> was added to the C++14 standard, libc++ implemented it, and then it was removed. Now (from the standard’s point of view), it is in limbo. I would like to move it into std/experimental; to make it clear that it’s not a part of the standard. Any objections? Anyone using it? — Marshall

Hi I have 2 question for you guys, 1. Which is the difference between this two methods? (select_datetime, datetime_select) 2. How I assign the selected date-time values, to an specific variable or array using select_datetime I know do it using datetime_select(''object'',''method'') I aprecciate your attention. Thanks PD: Sorry about my english.

I''ve become very fond of Yurii Rashkovskii''s "aspects". For such a simple change they make it a LOT easier to navigate, read and verify specs. Are there any plans to include something like this in RSpec? Ashley

Hi. I''m upgrading a project from an 0.8.0 pre-release gem to 0.8.2. I''ve installed the 0.8.2 gem, and the rspec_on_rails 0.8.2 plugin: ruby script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_8_2/rspec When I try to run my specs though, I get the below error. It''s as if the spec_helper cannot find "spec/rails". I''ve noticed that

I have to confess that I did not know about facets before reading Ashley Moran''s post: http://aviewfromafar.net/2007/10/21/quick-and-dirty-facets-in-rspec-trunk Not knowing about the facets solution, I made a couple of feature requests for nested describes: http://rubyforge.org/tracker/index.php?func=detail&aid=14980&group_id=797&atid=3152

Hi all, I''m not sure if I''ve missed it, but I couldn''t find any docs for stubbing an instance method on a class. For example: class Foo; end Foo.stub!(:my_instance_method).and_return(nil) The reason (I think) I need this is because a certain class (Test::Unit::TestCase) expects an argument (name of method) to new and throws an exception if that instance method

Rails 3.1.3 Globalize3 latest I am not sure if I can ask this question here in general Rails forum. But I''ll try. Currently I am using a gem, Globalize3, which is useful for model I18n. https://github.com/svenfuchs/globalize3 Say, I have a model City, having only one column, name. City names appear differently depending on the language, so perhaps this particular gem is useful.

Rspec is all about using natural language to define behavior. In this context, I feel that lambda is sorely out of place. I was chatting on #irc and a pal of mine (wycats) proposed an interesting alternative: alias_method :doing, :lambda so instead of something like lambda {post :create, {:title => nil}}.should raise_error(ActiveRecord::RecordInvalid) we get doing {post :create, {:title

I''m seeing some odd behavior around the should_receive() when given a block combined with some cardinality. For example, with the following... my_mock.should_receive(:foo).twice do |i| puts i end ... the spec passes but i never gets puts''ed. With the following... my_mock.should_receive(:foo) do |i| puts i end ... i gets puts''ed twice but the spec fails because

Hi, I''m developing a RESTful Rails application whose code and specs are becoming increasingly repetitive: every controller does pretty much the same set of things (give or take the occasional twiddle), for example, and so every controller spec is almost identical modulo some names, constants and strings. The make_resourceful plugin, which autogenerates the boilerplate REST