In part 1, I talked about the need to announce things to users in a Rails app. The announcements should be scheduled, shown to each user only once, and targeted to particular types of users.
We’re building a Ruby gem to enable this.
I started by writing tests, describing what the one-time announcements gem should do. Test driven development (TDD) can be controversial, but I find that it helps me plan and identify issues earlier in development.
I learned how to test from Everyday Rails Testing with RSpec. The author continually updates it as new versions of Rails and RSpec are released.
The first tests confirm, at the model level, that announcements can be:
- Marked as read
These tests pass with the current Announcement model:
Marking announcements as read
Each user should see a particular announcement only once, so I needed a way to mark announcements as read.
The unread_by scope above shows only those announcements which the user has not read. It uses the AnnouncementView model to see who has read which announcements:
The current method chains the ready_for_delivery, unread_by, and in_delivery_order scopes to determine which announcement to deliver.
In part 3, we’ll look at how to target announcements to particular types of users. For instance, what if you have an announcement just for users on a particular subscription plan?
Hired.com brings Rails job offers to you. Free for candidates. Salaries from $75,000 to $250,000. Sign up now!