← Back to Upcase

How Can I Speed Up My Tests?


(Scott Hollinshead) #1

I am using Rspec and Capybara to do some tests, but they seem quite slow how would i speed this up?

Spec Helper

# This file is copied to spec/ when you run 'rails generate rspec:install'
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'
require 'rspec/autorun'

# Requires supporting ruby files with custom matchers and macros, etc,
# in spec/support/ and its subdirectories.
Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f }

# Checks for pending migrations before tests are run.
# If you are not using ActiveRecord, you can remove this line.
ActiveRecord::Migration.check_pending! if defined?(ActiveRecord::Migration)

RSpec.configure do |config|
# ## Mock Framework
#
# If you prefer to use mocha, flexmock or RR, uncomment the appropriate line:
#
# config.mock_with :mocha
# config.mock_with :flexmock
# config.mock_with :rr

# Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
config.fixture_path = "#{::Rails.root}/spec/fixtures"

# If you're not using ActiveRecord, or you'd prefer not to run each of your
# examples within a transaction, remove the following line or assign false
# instead of true.
config.use_transactional_fixtures = true

# If true, the base class of anonymous controllers will be inferred
# automatically. This will be the default behavior in future versions of
# rspec-rails.
config.infer_base_class_for_anonymous_controllers = false

# Run specs in random order to surface order dependencies. If you find an
# order dependency and want to debug it, you can fix the order by providing
# the seed, which is printed after each run.
#     --seed 1234
config.order = "random"
config.include Capybara::DSL
end

static_pages_spec

require 'spec_helper'

describe "Static pages" do

  describe "Home page" do

    it "should have the content 'Sample App'" do
      visit '/static_pages/home'
      expect(page).to have_content('Sample App')
    end

    it "should have the title 'Home'" do
      visit '/static_pages/home'
      expect(page).to have_title('Ruby on Rails Tutorial Sample App | Home')
    end
end

describe "Help page" do

  it "should have the content 'Help'" do
    visit '/static_pages/help'
    expect(page).to have_content('Help')
  end

  it "should have the title 'Help'" do
    visit '/static_pages/help'
    expect(page).to have_title('Ruby on Rails Tutorial Sample App | Help')
  end
end

describe "About page" do

  it "should have the content 'About Us'" do
    visit '/static_pages/about'
    expect(page).to have_content('About Us')
  end

  it "should have the title 'About'" do
    visit '/static_pages/about'
    expect(page).to have_title('Ruby on Rails Tutorial Sample App | About')
  end
end

describe "Contact page" do

  it "should have the content 'Contact'" do
    visit '/static_pages/contact'
    expect(page).to have_content('Contact')
  end

  it "should have the title 'Contact'" do
    visit '/static_pages/contact'
    expect(page).to have_title('Ruby on Rails Tutorial Sample App | Contact')
  end
end
end

(Scott Hollinshead) #2

After carrying on with the tutorial, Michael Hartl recommended using spork to speed up the testing.


(Jon Seidel) #3

@scott… One of the causes of slow tests is that they have to start Rails each time you run a test, so a pre-loader can really help. I’ve used zeus with great resulsts (written in Go, I believe) and there’s also spring (pure-ruby) as well.

Here’s one post showing the improvement from spork to zeus and another moving from spork to spring.


(Scott Hollinshead) #4

@JESii I have looked into spring as @georgebrock told me about it.
After looking into spring, people are recommending binstubs is this a feature only for RVM? or can Windows users use it too?

Also are the binstumps necessary?

Thanks


(Jon Seidel) #5

@scott… Check out this stackoverflow post – sounds like it can help.


(Scott Hollinshead) #6

Thanks @JESii appreciate the help.