*
*
Rakefile
*
*
require(File.join(File.dirname(__FILE__), 'config', 'boot'))
require 'rake'
require 'rake/testtask'
require 'rake/rdoctask'
require 'ta
I tried putting the fixtures into a subfolder, next I'm trying to replicate
the behaviour in a blank project. Then you and the rails devs have a bit
more to play with.
On Thu, Jun 7, 2012 at 12:57 PM, David Chelimsky wrote:
> On Thu, Jun 7, 2012 at 6:29 AM, Rainer Kuhn wrote:
> > Follow up: is t
On Thu, Jun 7, 2012 at 6:29 AM, Rainer Kuhn wrote:
> Follow up: is there a way to set RSpec to be less forgiving on errors. If my
> specs would have failed because of that error I would have fixed it months
> ago. (Or at least reported it)
I can't duplicate this behavior myself, but from what I c
On Thu, Jun 7, 2012 at 6:26 AM, Rainer Kuhn wrote:
> I guess I can forward this issue to fixture builder, It only happens for
> fixtures that are in a module, like
> Event::Confirm
> Event::CriticalError
> Those fixtures propably need to either be named differently or to live in a
> module subfold
On Thu, Jun 7, 2012 at 6:17 AM, Rainer Kuhn wrote:
> My guess was wrong, it can't seem to handle empty fixtures yml files. The
> gist contains only a brief snippets of the actual log, but you can see that
> it's trying to load fixtures from multiple specs
>
> https://gist.github.com/2888253
>
> ca
Follow up: is there a way to set RSpec to be less forgiving on errors. If
my specs would have failed because of that error I would have fixed it
months ago. (Or at least reported it)
On Thu, Jun 7, 2012 at 12:26 PM, Rainer Kuhn wrote:
> I guess I can forward this issue to fixture builder, It onl
I guess I can forward this issue to fixture builder, It only happens for
fixtures that are in a module, like
Event::Confirm
Event::CriticalError
Those fixtures propably need to either be named differently or to live in a
module subfolder.
So, nothing wrong with RSpec, I am very sorry that I put th
My guess was wrong, it can't seem to handle empty fixtures yml files. The
gist contains only a brief snippets of the actual log, but you can see that
it's trying to load fixtures from multiple specs
https://gist.github.com/2888253
cat event_critical_errors.yml
--- {}
Users/rainer/work/app_path/s
On Thu, Jun 7, 2012 at 5:54 AM, David Chelimsky wrote:
> On Thu, Jun 7, 2012 at 4:00 AM, Rainer Kuhn wrote:
>> I narrowed it down to three things, the first one might be interesting to
>> you, the other ones are my problem, although probably common among lots of
>> projects:
>>
>> Since we don't
On Thu, Jun 7, 2012 at 4:00 AM, Rainer Kuhn wrote:
> I narrowed it down to three things, the first one might be interesting to
> you, the other ones are my problem, although probably common among lots of
> projects:
>
> Since we don't mock we usually need a bit of test data prepared for each
> tes
I narrowed it down to three things, the first one might be interesting to
you, the other ones are my problem, although probably common among lots of
projects:
Since we don't mock we usually need a bit of test data prepared for each
test. At first we used factories, but setting things up every time
11 matches
Mail list logo
