Let’s say I change a method in one of my models in a Rails app.
I hit save: autospec kicks in and starts specing.
But I haven’t yet edited my spec(s) to the new method name so the specs
will obviously fail, but I already know that. So I edit my specs.
Autospec will run a second time (or even more if more than one spec file
is changed).
But I haven’t yet edited my controller(s) to reflect the new change(s),
so I edit more files and save, therefore Autospec will run again.
In such case (which happens often), autospec has been running a few
times for nothing. Would it be possible to implement a sort of timeout
(like 10") to let us make additional changes to other files before
autospec starts his job? It’s pretty annoying to have growl display
plenty error messages as we already know specs will fail.
But I haven’t yet edited my controller(s) to reflect the new
change(s),
so I edit more files and save, therefore Autospec will run again.
In such case (which happens often), autospec has been running a few
times for nothing. Would it be possible to implement a sort of timeout
(like 10") to let us make additional changes to other files before
autospec starts his job? It’s pretty annoying to have growl display
plenty error messages as we already know specs will fail.
so I edit more files and save, therefore Autospec will run again.
In such case (which happens often), autospec has been running a few
times for nothing. Would it be possible to implement a sort of timeout
(like 10") to let us make additional changes to other files before
autospec starts his job? It’s pretty annoying to have growl display
plenty error messages as we already know specs will fail.
The problem is I would want feedback asap on a fail. The faster I get
feedback the earlier I realize I’ve broken something and the easier it
will be to localise the error. I think getting error messages I already
know about is easily worth the sacrifice of this.
Let’s say I change a method in one of my models in a Rails app.
I hit save: autospec kicks in and starts specing.
But I haven’t yet edited my spec(s) to the new method name so the
specs
will obviously fail, but I already know that. So I edit my specs.
Autospec will run a second time (or even more if more than one spec
file
is changed).
Why are you routinely changing the code without updating the specs in
advance?
Why are you routinely changing the code without updating the specs in
advance?
That’s not the point of my question.
I learnt early on when I joined this list, that whenever I ask a
question of the form “When I do XXX, I get weird/undesirable
behaviour, how do I avoid it?”, 90%+ of the time the answer is of the
form “Don’t do XXX.”*. What you were describing sounded like
something you shouldn’t be doing often enough to worry about it’s
consequences, but I wanted to rule that out first…
Ashley
Probably half the emails I write to rspec-users I delete without
sending, because by the time I’ve explained the problem in enough
detail, I realise I’ve answered my own question
Probably half the emails I write to rspec-users I delete without
sending, because by the time I’ve explained the problem in enough
detail, I realise I’ve answered my own question
Probably half the emails I write to rspec-users I delete without
sending, because by the time I’ve explained the problem in enough
detail, I realise I’ve answered my own question
