Before Ruby 2.5, if we wanted to log a caught exception, we would need to format it ourselves.
But from this version, It has been proposed to add the
Exception#full_message method to print the caught exception using the same format that Ruby uses while printing an uncaught exception.
This article will focus on improving tests in two ways:
- refactoring common parts of the test suite that are repeated many times
- speeding up the test suite by reducing database requests.
Have you ever needed inspecting a gem in your local machine?
For example, you need to figure out how a method works, to check the internal state or just out of curiosity.
This article describe 2 techniques to do so.
For illustration he implements a simple comments page.