Clients and Wrappers (also referred to as “Facades”) are remarkably useful tools for working with external services, libraries or APIs. While both Clients and Wrappers are primarily used to facilitate usage of before-mentioned libraries or APIs, there are some significant differences in responsibilities each of these patterns have. In some cases a Wrapper can take over a Client’s responsibilities too
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.
Query Objects (also referred to as queries) is another pattern that helps in decomposing your fat ActiveRecord models and keeping your code both slim and readable. While this article is written with Ruby On Rails in mind, it easily applies to other frameworks, especially MVC based and applying ActiveRecord pattern.
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?
Everything started with the idea of making web applications simpler and easier. It was David Heinermaier Hansson who put forward his concept and found other enthusiasts who, as the Rail Coreteam, created and expanded the Ruby on Rails Framework, a powerful development platform today.
