test-queue

makes your TESTS

RUN FAST

tmm1/test-queue

HOW?

DISTRIBUTE THE LOAD

WITH CORES USE THEM IF YOU HAVE THEM

BRING YOUR OWN

USE SOMEONE ELSE'S

THERE ARE SO MANY CLOUDS OUT THERE

WHICH CLOUD?

PICK ONE I AM NOT HERE TO SELL YOU ANYTHING

BUT NO, REALLY, HOW?

1. TAKE A SOCKET

2. FORK SOME WORKERS

3. SMARTLY DISTRIBUTE TESTS

4. SPEND LESS TIME WAITING ON CI

5. SPEND MORE TIME SHIPPING CODE

GETTING STARTED

INSTALL # Gemfile group :test do gem "test-queue" end

ANATOMY OF A SCRIPT/TEST-QUEUE #!/usr/bin/env ruby $LOAD_PATH.unshift File.expand_path("./../../rspec", __FILE__) unless ENV["TEST_QUEUE_WORKERS"] abort "TEST_QUEUE_WORKERS must be set in env!" end require "test_helper" require "test_queue" require "test_queue/runner/rspec" class CustomTestRunner < TestQueue::Runner::RSpec end CustomTestRunner.new.execute

SETTING UP YOUR AFTER_FORK class RailsRSpecRunner < TestQueue::Runner::RSpec def after_fork(num) # ActiveRecord ActiveRecord::Base.configurations["test"]["database"] << num.to_s ActiveRecord::Base.establish_connection(:test) # Redis $redis.client.db = num $redis.client.reconnect end end

SETTING UP YOUR PREPARE class RailsRSpecRunner < TestQueue::Runner::RSpec def prepare(num) # grab a copy of your database schema num.times do |i| # load it into a clean copy of your test database end end end

DEMO

ADVANCED USAGE AT A HIGH LEVEL

REMOTE WORKERS

AN EXAMPLE # shared secret export TEST_QUEUE_RELAY_TOKEN=12345 # tell us what you're doing export TEST_QUEUE_VERBOSE=1 # create a master test-queue instance TEST_QUEUE_SOCKET=1.2.3.4:12345 bundle exec rspec-queue # on a server, far, far away... # create a worker that sends results back to the master TEST_QUEUE_RELAY=1.2.3.4:12345 bundle exec rspec-queue

COMBINE WITH YOUR CI SYSTEM

RUN YOUR TESTS FASTER

THANKS I AM @WFARR

GITHUB.COM/WFARR/SIX_MINUTE_BLOG !⚡ GITHUB.COM/TMM1/TEST-QUEUE