Sandi Metz' Rules For Developers
Back in January, Sandi Metz introduced her rules for developers in a Ruby Rogues podcast episode episode. Around the time Sandi’s rules were published, the team I am on was starting a new project. This post details the experience of that team applying Sandi’s rules to the new application. The rules _There are four rules._ Here are the rules: Classes can be no longer than one hundred lines of code.
Using `yield_self` for composable ActiveRecord relations
Ruby 2.5 introduces Object#yield_self, which can be thought of as a close cousin to Object#tap. Where tap executes a block returning the value it’s called on, yield_self yields the object its called on into the supplied block, returning the result of the block. Many have compared yield_self to Elixir’s pipe operator, |>, and while I use and enjoy the pipe operator in Elixir, I had a hard time envi
PostgreSQL's Foreign Data Wrapper
Have you ever needed to write a query that combined data from two PostgreSQL databases? Our client Healthify has. Since Healthify work with healthcare and store some patient information, they’re very careful not to send any personally identifiable information to third party services. One such service is Segment, which Healthify use to track user activity on the site. Conveniently, Segment can send
Headless Capybara Feature Specs with Chrome
I’ve been a happy user of Capybara-WebKit for many years now, but its dependence on Qt can make it frustrating to install on macOS, particularly following macOS or Xcode updates. One such recent issue lead me to experiment with running my tests in Chrome via ChromeDriver and Selenium. I found the installation of ChromeDriver and Capybara-Selenium to be significantly faster than the installation of
Acceptance Tests with Subdomains
You’re excited about building a new application which allows users to sign up and host their own blog. You decide that each blog will have their own space by providing a subdomain. Let’s start off with a feature spec. require "rails_helper" feature "user views a blog" do scenario "homepage" do blog = create( :blog, subdomain: "bobloblaw", title: "Bob Loblaw's Law Blog", description: "Welcome to my
Creating your first iOS Framework
If you’ve ever tried to create your own iOS framework, you know that it’s not for the faint of heart – managing dependencies and writing tests doesn’t make it any easier. This tutorial will walk you through creating your first iOS framework from start to finish so that you can go out and create your own. We’re going to build a framework that exposes a function called RGBUIColor(red:green:blue) tha
Process Jobs Inline when Running Acceptance Tests
Web apps often move long-running processes (such as delivering email) out of the request/response cycle into a queue of background jobs. A worker process then picks up those jobs from the queue and runs them in the background. In acceptance tests, it’s desirable to run those background jobs immediately, skipping the queueing component, to avoid writing custom code to work the jobs off. Configure R
Paid Private Repos for Hound
In April, we announced Hound, a hosted service that comments on Ruby style guide violations in your GitHub pull requests. Since then, about 2,000 users have signed up for Hound. We have been hard at work across 127 commits making Hound faster and more reliable. Recently, Hound has been reviewing about 7,000 GitHub pull requests across about 300 GitHub repos each week. What people are telling us We
Automatically Wait for AJAX with Capybara
We have a race condition between click_link and reload_page. Sometimes the AJAX call will go through before Capybara reloads the page, and sometimes it won’t. This kind of nondeterministic test can be very difficult to debug, so I added a little helper. Capybara’s Little Helper Here’s the helper, via Coderwall: # spec/support/wait_for_ajax.rb module WaitForAjax def wait_for_ajax Timeout.timeout(Ca
Workflows for Writing Migrations With Rollbacks in Mind
thoughtbot’s dotfiles include an alias mapping migrate to rake db:migrate db:rollback && rake db:migrate It is also a good practice in our workflow to use the migrate alias in place of rake db:migrate. Let’s explore what this command does and why we recommend it. Reversibility rake db:migrate db:rollback will run any pending migrations and then attempt to roll back those migrations. If the migrati
How to Share a Session Between Sinatra and Rails
As Rails developers, we run into Sinatra apps all the time: gems such as Resque which expose a dashboard via Sinatra, legacy Sinatra apps that run alongside a main Rails app, and Sinatra APIs embedded within a Rails app, to name a few examples. Here’s a common problem: how do you share authentication between the apps? It would be really convenient to be able to do something like this in our Sinatr
Using GDB to Inspect a Running Ruby Process
This job shouldn’t be taking this long! That’s not a great thing to have to say, is it? However, I bet you’ve said it before and may not have immediately know why. With liberal use of puts and maybe pry, you can figure out what a problem might be next time you run it, but sometimes you need to figure out what that problem is right now. As it turns out, and I know this is a shocker, Ruby processes
Use Factory Bot's build_stubbed for a Faster Test Suite
Want to speed up your test suite? Reduce the number of objects persisted to the database. With Factory Bot, this is really easy; instead of using build or create to instantiate your models with data, use build_stubbed! build_stubbed is the younger, more hip sibling to build; it instantiates and assigns attributes just like build, but that’s where the similarities end. It makes objects look like th
Parallel Gem Installing Using Bundler
Do you realize how much time you’ve spent running bundle install? ] No more sword fighting! Bundler 1.4.0 adds support for parallel installation. You can pass in --jobs SIZE as a parameter to bundle config1. I recommend setting the size to one less the number of CPU cores on your machine2. But Prem, how much time could I save Let’s benchmark this! I’m going to run bundle install on a freshly-creat
Strong Parameters As Documentation
Besides moving attribute whitelisting to the controller rather than the model, Rails 4’s move to Strong Parameters over attr_accessible provides great documentation about the data with which records are being created. strong_parameters are good and you should feel good Here is an example of a controller many of us have written, using strong_parameters: class CommentsController < ApplicationControl
Better serialization, less as_json
# app/models/user.rb class User < ActiveRecord::Base has_secure_password has_many :posts end # app/models/post.rb class Post < ActiveRecord::Base belongs_to :user end # app/controllers/posts_controller.rb class PostsController < ApplicationController def show @post = Post.find(params[:id]) render json: @post.as_json( only: [:id, :content, :created_at], include: { user: { only: [:id, :username] } }
Better Acceptance Tests with Page Objects
During my Test-Driven Rails workshop earlier this week (which is also available as an online workshop), my students and I were writing acceptance tests surrounding marking todo items as complete. The spec looked like this: feature 'Manage todos' do scenario 'view only todos the user has created' do sign_in_as 'other@example.com' create_todo_titled 'Lay eggs' sign_in_as 'me@example.com' user_should
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Write Reliable, Asynchronous Integration Tests With Capybara
How to Find Missing or Unused I18n Translations
Code that says why it does