StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I found unit tests to be the most efficient, effective and powerful tool. So, before making any change, make sure your application has a minimum LOC so that you won't break any existing feature working on.</p> <p>You should care about unit tests (of course I'm talking about unit/functional/integrational tests) because:</p> <ul> <li>they ensure you won't break any existing feature</li> <li>they describe the code so that you won't need tons of comments everywhere to understand why that code fragment acts in that way</li> <li>having test you'll spent less time debugging and more time coding</li> </ul> <p>When you have tests, you can start refactoring your app. Here's a list of some tools I usually work with:</p> <ul> <li><a href="http://Rack::Test" rel="nofollow noreferrer">Rack::Bug</a></li> <li><a href="http://www.newrelic.com/get-RPM.html" rel="nofollow noreferrer">New Relic</a></li> </ul> <p>You might want to view some of the wonderful <a href="http://railslab.newrelic.com/" rel="nofollow noreferrer">Gregg's videos</a> about Scaling Rails to get more powerful tools.</p> <p>Also, don't forget to immediately start tracking how your application is performing and whether it is raising exceptions. You can use one of the following tools</p> <ul> <li><a href="http://www.hoptoadapp.com/" rel="nofollow noreferrer">Hoptoad</a></li> <li><a href="http://getexceptional.com/" rel="nofollow noreferrer">Exceptional</a></li> </ul> <p>If you need to fix some bug, don't forget to reproduce the issue with a test first, then fix the bug.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload