Amiruddin Nagri wrote: > On Wed, Sep 22, 2010 at 10:53 PM, Marnen Laibow-Koser > <[email protected]>wrote: > >> >> 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.
Don't run them against the production *database*! > > Deleting the spec folder sounds ok, But it isn't. > 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. No...you're trying to define an isolation point where there really isn't one. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
