In the previous post, we saw how to test time logic. In this post, I will share 3 common issues in specs and how to improve them.
You finished working on a ticket, all specs are passing locally, and you submit a PR. But today isn’t that day, the PR fails to build and it seems not only your PR but all builds are failing on that repository. You pause the music, mutter to yourself a curse and dig in the logs to discover that a set of specs contain a hard-coded date value, which is yesterday. How to prevent this? That’s what we will discover in this post.
From generating UUIDs for a new column to fixing legacy data, we need to write a custom script to achieve this.
I worked recently on migrating lambda functions to a Rails backend.
If you have worked on a Rails project, it’s guaranteed to come across callbacks. We will see in this post a refactoring example and how to use them safely. Let’s get started :smiley:
I was working recently on a Rails project and I faced an interesting behavior of
delete_all from ActiveRecord. In this post, I’ll go through the steps that I have done to understand what happened and how I did manage to get around it.
Background jobs are used a lot in production. At first, the concept may seem complex or unclear why we are using it. So without a lengthy introduction let’s jump into action with a simple example.
Did you get
RuntimeError: can't add a new key into hash during iteration error?
I saw a lot of projects where the default date format was used. In fact, customizing the date format to provide a human-readable date will be very welcomed from your customers!