Hey Lille.
> Specifically, what is the recommended structure for the test of the
> module filter;
>
How about creating a shared example group, and referencing that?
http://blog.davidchelimsky.net/2010/11/07/specifying-mixins-with-shared-example-groups-in-rspec-2/
> next, how can I confirm that
Hi,
I'm using rspec-rails (1.3.2), and wondering how to save myself the
trouble of testing filters for ActionControllers when those filters
call methods included from modules.
Specifically, what is the recommended structure for the test of the
module filter; next, how can I confirm that the contr
Hi David,
I've sent a patch for this problem via github.
Please check it out.
Thank you,
Nori
On Fri, Jan 14, 2011 at 12:18 PM, Nori Hamamoto wrote:
> Sounds good!!
>
> Nori
>
> On Fri, Jan 14, 2011 at 10:57 AM, David Chelimsky wrote:
>
>> On Jan 14, 2011, at 7:29 AM, Nori Hamamoto wrote:
>>
On Fri, Jan 14, 2011 at 11:05 AM, David Chelimsky wrote:
> On Jan 14, 2011, at 9:56 AM, Michael Guterl wrote:
>
>> I keep seeing strange run times for our specs:
>>
>> Finished in -348317500.25314 seconds
>>
>> Any thoughts are much appreciated.
>
> Are you stubbing Time.now anywhere?
Yes we are,
We're migrating a Rails 2.3.x application to Rails 3 and RSpec 2.x.
In Rails 2.3.x we were using
https://github.com/freelancing-god/after_commit to provide
after_commit functionality (now provided by Rails 3).
The plugin version of after_commit came with some helpers to make
testing with `use_tran
On Jan 14, 2011, at 9:56 AM, Michael Guterl wrote:
> I keep seeing strange run times for our specs:
>
> Finished in -348317500.25314 seconds
>
> Any thoughts are much appreciated.
Are you stubbing Time.now anywhere?
___
rspec-users mailing list
rspec-
Additionally, this problem doesn't happen when I use autospec on simple ruby
rb file, but only happens with rails.
On Fri, Jan 14, 2011 at 12:29 PM, Nori Hamamoto wrote:
> Hi there,
>
> I met a problem when I'm using RSpec(1.3.0) on rails.
> I installed rspec(1.3.1) and rspec-rails(1.3.3) instal
Hi there,
I met a problem when I'm using RSpec(1.3.0) on rails.
I installed rspec(1.3.1) and rspec-rails(1.3.3) installed through rails
script/plugin install from github.
I run autospec at $RAILS_ROOT, and if the test goes successful, it's no
problem, but once I get failed case, it keep running t
Sounds good!!
Nori
On Fri, Jan 14, 2011 at 10:57 AM, David Chelimsky wrote:
> On Jan 14, 2011, at 7:29 AM, Nori Hamamoto wrote:
>
> I said I'm using the newest version on the repository, but I mean that the
> newest version of rspec1's repository.
> I didn't try it on rspec2 because according t
I keep seeing strange run times for our specs:
Finished in -348317500.25314 seconds
Any thoughts are much appreciated.
Best,
Michael Guterl
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Jan 14, 2011, at 7:29 AM, Nori Hamamoto wrote:
> I said I'm using the newest version on the repository, but I mean that the
> newest version of rspec1's repository.
> I didn't try it on rspec2 because according to rspec2's git repository, it
> doesn't support rails 2 and I'm using rails 2.
>
I said I'm using the newest version on the repository, but I mean that the
newest version of rspec1's repository.
I didn't try it on rspec2 because according to rspec2's git repository, it
doesn't support rails 2 and I'm using rails 2.
Sorry about the lack of the information in my report.
Cheers,
On Jan 14, 2011, at 12:19 AM, Nori Hamamoto wrote:
> Hi there,
>
> I've just started using rspec and rspec-rails (both are the newest version on
> git repository).
> I met some inconsistently behavior on it method and its method.
> The following is the way to reproduce it:
>
> command line:
>
13 matches
Mail list logo
