Sunday, October 3, 2010
On Wed, Sep 22, 2010 at 10:53 PM, Marnen Laibow-Koser <lists@ruby-forum.com> wrote:
I will be very skeptical about running tests against production servers, what if by mistake I corrupt the data or drop the database itself.
Deleting the spec folder sounds ok, but there are also many test configuration files floating around that are not need for eg environments/test.rb etc. What about them ?
Rails is clearly missing the isolation for the necessary final executable code and rest of the files required for eg testing etc. It is much more clearly defined in Java world.
--
But it would be best to keep the tests. If you run into a problem on
your production server, you should be able to run the tests to see where
things are going wrong.
I will be very skeptical about running tests against production servers, what if by mistake I corrupt the data or drop the database itself.
Deleting the spec folder sounds ok, but there are also many test configuration files floating around that are not need for eg environments/test.rb etc. What about them ?
Rails is clearly missing the isolation for the necessary final executable code and rest of the files required for eg testing etc. It is much more clearly defined in Java world.
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@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment