If we type Ruby on Rails 2019 in Google we will most likely get results from blog posts and forums dedicated to Ruby’s alleged death, but the truth is, Ruby is doing great and still remains a good technology to choose in 2019 and here is why.
In the previous part of this article we focused on making specs we try to write as readable as possible. This however, comes at a cost of duplication and bloated individual tests. While this is a cost we intend to pay, there are ways to mitigate the impact of readability oriented specs on the overall size of our suite.
In part 1 we have covered antipatterns related to stubbing and problem with implementation details that are a overcomplicated just for the sake of being super easy to tests. In second part we are going to focus more on tests themselves.
When preparing our test suite we might be tempted to make some shortcuts that will render our tests less readable, comprehensible or will significantly decrease the flexibility of further implementation. Below, I try to list some of the most commonly seen techniques we should avoid to keep our test suite healthy.
It is hard to underestimate a value and importance of automated tests. Creating confidence about if the code works the right way and thus enabling safe refactoring is just one thing. Another one is that test suite can act as a way to document behavior and also, especially when approached the BDD way, can drive the code design and architecture.
With Ruby on Rails as our primary backend technology, we have developed a set of practices for testing our applications. Our goal was to maximize the efficiency of writing tests that cover the most critical parts of the software built.
Before starting development on a legacy project, we are often asked to do a quick review of its quality. Some projects are easy to analyze and the task just boils down to a look into a couple of classes, routes file, tests etc.
As I predicted last time Ruby’s popularity is still growing. Being named a Language of the Year in 2006, it now has the highest position since 2001. According to TIOBE Index for May 2016 Ruby is currently at position 8 and maybe, there is another chance for Ruby on Rails to conquer the world.
When we start checking what technologies stand behind endless apps we happen to use or just encounter every day, we will often hear Ruby on Rails. Who should know what it is and who can benefit from learning how the Rails framework functions?
