* Ash Moran [2011-08-30]:
> I'm trying to optimise my spec run time. I have 123 examples so far,
> which run in ~4.2 seconds on average. But 116 of those will run in
> ~0.18 seconds. So, obviously, I only want to run the slow ones when I
> change that code.
I have a similar situation with the slow
Yeah sorry I realised that was what was happening.
But thought I'd ask the question in case there might have been something I
was missing (in the docs) or a smart hack ;-)
On 30 August 2011 14:34, David Chelimsky wrote:
> On Aug 29, 2011, at 6:09 PM, Shane Mingins wrote:
>
> Hi
>
> We have the
On Aug 29, 2011, at 6:09 PM, Shane Mingins wrote:
> Hi
>
> We have the occasional ApplicationController before_filter that is
> conditioned by the Rails.env and we like the following style:
>
> before_filter :check_for_something if Rails.env == 'production'
This approach won't work because t
On Mon, Aug 29, 2011 at 9:24 AM, Ash Moran wrote:
> it "prints an error" do
> ignoring_errors {
> run_command(%w[ missing_wallet.dat ])
> }
> stream_bundle.captured_error.should eq "Couldn't find wallet file:
> missing_wallet.dat\n"
> end
>
> Now obviously that wouldn't be h
Hi
We have the occasional ApplicationController before_filter that is
conditioned by the Rails.env and we like the following style:
before_filter :check_for_something if Rails.env == 'production'
And wish to spec this in an ApplicationController spec using an anonymous
controller (e.g.
http://
Hi all (again)
Sorry for the new thread, but I don't have a copy of my own email in my inbox
to reply to.
Anyway I managed to cobble together a hack to make Guard filter slow specs by
default, but unfilter them if the slow file itself was changed. I've Gisted the
relevant sections of my Guardf
Hi all
I'm trying to optimise my spec run time. I have 123 examples so far, which run
in ~4.2 seconds on average. But 116 of those will run in ~0.18 seconds. So,
obviously, I only want to run the slow ones when I change that code.
I've added `adapter: :slow` to the offending example group, whic
On 29 Aug 2011, at 20:09, Nick wrote:
> Hey there, Ash. Why not put your call to #run_command inside a begin-rescue
> statement?
Hi Nick
Yes I'm missing the obvious as usual* :-)
Well I guess I could, but the syntax then is even more intrusive. I guess I
just want the lightest way possible t
Hey there, Ash. Why not put your call to #run_command inside a begin-rescue
statement?___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Hi all
Long time since I've posted to rspec-users. Glad to see the place is still here
and hope you're all well :-)
I have a question about ignoring exceptions when they're not interesting. For
example, I have a few cases in my code along these lines…
it "prints an error" do
expect {
I've shared my solution here in case it's of
interest: https://gist.github.com/1178383
I don't like the use of reload_routes! but it seems to do the trick.
Regards, Nick
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman
Hi David
Something like:
Given I am a user about to receive an arbitrary flash notice
When I visit one of the application's static pages which has not yet been
cached
Then I should not see my flash notice in the page
And another user should not see my flash notice when they visit the same
pag
12 matches
Mail list logo
