Rails%203%20In%20Action

Reason #4: emphasis on testing
of your application and can be used as a set of instructions explaining exactly how this
feature works. This is a great way to verify that the feature is precisely what was
requested.
As you write these tests for the application, you provide a safety net for if things go
wrong. This collection of tests is referred to as a test suite. When you develop a new feature,
you have the tests that you wrote before the feature to prove that it’s working as
you originally thought it should. If you want to make sure that the code is working at
some point in the future, then you have the test suite to fall back on.
If something does go wrong and it’s not tested, you’ve got that base to build
upon. You can write a test for an unrealized situation—a process known as regression
testing—and always have that test in the future to ensure that the problem does not
crop up again.
545