it Ctrl+C), only when it
re-runs a changed spec. And not every time, only occasionally.
I've started running autotest with the -v option to try and figure out
what it's doing.
Regards,
Matt
--
Matt Mower :: http://matt.blogs.it/
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
e weeks ago, but to avoid this type of problem.
> I may have screwed up, or perhaps you've got a mix of requires from
> older gen'd specs and newer ones.
>
I'm not sure what "paths in your generated specs" means to check this myself.
Regards,
Matt
--
Matt Mower ::
reproduce this, please let me know.
>
That's quick work David, thanks ;-)
I'm still not entirely sure which version of rspec I should be running
for Rails 2.1. Is edge a reasonable safe choice? Should I stick with
1.1.4 and wait for 1.1.5. I'm not sure how to make th
dn't seem to
be having an effect. I emailed Brian but I think he was at rails conf
so I guess he may be fighting a backlog of work/email.
Is there any likelyhood of any_instance making it into RSpec proper?
If not, has anyone else had any luck implementing it?
Regards,
Matt.
--
rom the previous runs). If I
ctrl+c to run all specs it runs the controller spec again. If I resave
the controller the change is again detected but the spec is not run.
I'm using Rails 2.1, edge rspec & rspec-rails, and ZenTest 3.9.2
Anyone else seen this?
Matt.
--
Matt Mower :: http:/
tly still using
Subversion and I've not found a good way of managing Git externals in
this setup.
Another argument for switching the project to Git I guess...
Thanks David.
M.
--
Matt Mower :: http://matt.blogs.it/
___
rspec-users mail
chives of this list but couldn't find an
article where you (or anyone else) expands on this view about
any_instance.
And thanks for the pointer, I guess I will try and assemble the patch
and see if I can make it work.
Regards,
Matt.
--
Matt Mower :: http://matt.blogs.it/
_
On Wed, Jun 4, 2008 at 2:18 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> This just got fixed a few hours ago. Grab the latest from
> git://github.com/dchelimsky/rspec.git.
>
It's not fixed for me. My copy of rspec was installed after the commit
that closes #369.
regar
On Wed, Jun 4, 2008 at 2:18 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> On Jun 4, 2008, at 8:15 AM, Matt Mower wrote:
>
>> I know this isn't autotest-users but I'm not sure where else to bring this
>> up:
>>
>> [["app/controllers/cont
, git compatible,
"script/plugin update" takes care of the details?
M.
--
Matt Mower :: http://matt.blogs.it/
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
spec suite that already works but for the
lack of any_instance.
I'm all for encouraging good practice and wrapping any_instance in the
shame of your peers. But I'm also all for being pragmatic. Does your
patch work? I wasn't clear whethe
of Array.
The error occurred while evaluating nil.size
But no stack trace. Shouldn't I get a stack trace?
Regards,
Matt.
--
Matt Mower :: http://matt.blogs.it/
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
12 matches
Mail list logo
