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
On Thu, Jun 7, 2012 at 4:00 AM, Rainer Kuhn rai...@incutio.com 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
On Thu, Jun 7, 2012 at 5:54 AM, David Chelimsky dchelim...@gmail.com wrote:
On Thu, Jun 7, 2012 at 4:00 AM, Rainer Kuhn rai...@incutio.com 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
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
--- {}
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
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 rai...@incutio.com wrote:
I guess I can forward this issue to
On Thu, Jun 7, 2012 at 6:17 AM, Rainer Kuhn rai...@incutio.com 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
On Thu, Jun 7, 2012 at 6:26 AM, Rainer Kuhn rai...@incutio.com 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
On Thu, Jun 7, 2012 at 6:29 AM, Rainer Kuhn rai...@incutio.com 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,
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 dchelim...@gmail.comwrote:
On Thu, Jun 7, 2012 at 6:29 AM, Rainer Kuhn
On Wed, Jun 6, 2012 at 5:14 AM, Rainer Kuhn rai...@incutio.com wrote:
[This is my third and final attempt to post to this group, first 2 were with
google groups]
The google group is a mirror of the rspec-users list, but for that to
work you actually have to post to the rspec-users list, not the
I have started with a blank spec_helper and I'm seeing lots of improvements
regarding the focus tag. Not the 12sec load time however. Let me do some
legwork first and I present you with the results in a couple of hours.
Tomorrow perhaps since I have a couple of hours of urgent dev work my list.
On Wed, Jun 6, 2012 at 6:38 AM, Rainer Kuhn rai...@incutio.com wrote:
I have started with a blank spec_helper and I'm seeing lots of improvements
regarding the focus tag. Not the 12sec load time however. Let me do some
legwork first and I present you with the results in a couple of hours.
13 matches
Mail list logo
