Marnen Laibow-Koser wrote:
> If you're going to do that, then it's probably better to declare a
> function that will do all that so you don't have to rely on the up-arrow
> key. But why not just use autotest?
Sure, I can make it easier with a function, that was just the first
version I got working.
As I understand it, autotest runs each test normally, by starting up a
new rails environment. It takes over 10 seconds for our rails
environment to start. (We've tried to get it to start quicker, but
that's a whole other topic.) I need to be able to make a change to a
test or code and run the test immediately without the 10 second wait.
> Depending on what you're changing, you may well want to restart Rails
> each time to ensure that it's loading current code.
That's what I'm trying to avoid. That's what the load and reload!
commands are hopefully doing.
> Well, you may not be getting good test isolation -- there's the
> potential for old test runs to influence new ones. And it's more work
I'm only running 1 test in the above example, "test_example1". And I
instantiate a new ExampleTest each time. How could this lead to and old
test influencing a new one?
--
Posted via
http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk@...
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en-~----------~----~----~----~------~----~------~--~---
