TestTrack is an open-source split-testing and feature-toggling system written in Ruby on Rails.

• Uses a stateful server to provide consistent experiences for customers across devices, and allow for bulk assignment overrides.
• Rich client libraries available for multiple platforms optimized to minimize time-to-glass and gracefully degrade if the server is unavailable.
• Designed to streamline developer and PM workflow - focusing on designing and running your tests, not the plumbing, and reducing incidence of implementation mistakes that can hurt your data.
• Provides an optional Chrome extension to allow your team to interactively override their split assignments.
• TestTrack is not an analysis tool. It focuses on fast, trustworthy, and robust split assignment and identity management, leaving analysis to the great tools that already exist, and those that are yet to come.

Check out the Rails at Scale talk for some background on why we built it and some of the key design decisions behind TestTrack:

The TestTrack system consists of the following components:

• the server (this repository)
• the Rails client
• the JS client
• the Chrome extension

The list of requirements to configure a TestTrack server are:

• Ruby 2.2.3+
• Postgresql 9.4+

1. git clone https://github.com/Betterment/test_track
2. bundle install
3. bundle exec rake db:setup
4. bundle exec rails server

At this point, you've got a working installation and can proceed to setting up the Rails client in order to create your first split.

TestTrack is designed to deploy as a conventional 12-factor application.

Required environment variables:

• DATABASE_URL -- the url to your Postgresql database server

In order to use the JS client, you will need to specify the set of hosts that will be making CORS requests to your TestTrack server. That can be set via the WHITELIST_CORS_HOSTS environment variable.

export WHITELIST_CORS_HOSTS=yoursite.example.org,othersite.example.org

In order to use the TestTrack Chrome extension, you will need to set up the BROWSER_EXTENSION_SHARED_SECRET environment variable. Details.

There are a few things that you will need to do in the TestTrack application:

• Create Apps -- client applications that will manage splits on your TestTrack server
• Create Admins -- users that can access the admin features of the TestTrack server
• Manage splits using the admin features

In order to create spilts in your client applications, you will need to register that client application with your TestTrack server. Run the following in a rails console.

> App.create!(name: "[myapp]", auth_secret: SecureRandom.urlsafe_base64(32)).auth_secret
=> "[your new app password]"

This is the password that you should plug into your client application's TEST_TRACK_API_URL.

At Betterment, we run TestTrack in every environment, including our laptops, which enables engineers to override splits with the Chrome extension while they code.

TestTrack provides a Rake task to make it easier to set up apps that automatically get reloaded whenever you recreate your TestTrack database. If you want to add a rails app called widget_maker to TestTrack, run:

rake seed_app[widget_maker]

This will do three things:

• Find or create a file called db/seed_apps.yml
• Find or create an entry in it for your app name and set a randomly generated auth_secret
• Run rake db:seed, which reloads your seed apps into the database

Note that db/seed_apps.yml is .gitignored so you can run TestTrack locally without having a private copy of the test_track repository or having uncommitted changes on your local checkout. That way it's easier to contribute to TestTrack, and stay on the latest version of the open source product.

You can use a configuration management tool like boxen to install TestTrack and inject a custom seed_apps.yml file for your team.

In order to access the admin features of the TestTrack server, you must create an Admin in your database. Run the following in a rails console.

> Admin.create!(email: "[email protected]", password: "[something secret]")

A Rails application that manages Splits on the TestTrack server.

A member of your team that administers the weightings of splits, deciding a the winning variant of a split, and uploading one-off visitor assignments.

A person using your application.

A feature for which TestTrack will be assigning different behavior for different visitors.

Split names must be strings and should be expressed in snake_case. E.g. homepage_redesign_late_2015_experiment, signup_button_color_experiment, or invite_button_enabled.

One the values that a given visitor will be assigned for a split, e.g. true or false for a classic A/B test or e.g. red, blue, and green for a multi-way split. Variants may be strings or booleans, and they should be expressed in snake_case.

Variants are assigned pseudo-randomly to visitors based on their visitor IDs and the weightings for the variants. Weightings describe the probability of a visitor being assigned to a given variant in integer percentages. All the variant weightings for a given split must sum to 100, though variants may have a weighting of 0.

A name for a customer identifier that is meaningful in your application, typically things that people sign up as, log in as. They should be expressed in snake_case and conventionally are prefixed with the application name that the identifier is for, e.g. myapp_user_id, myapp_lead_id.

We would love for you to contribute! Anything that benefits the majority of test_track users—from a documentation fix to an entirely new feature—is encouraged.

Before diving in, check our issue tracker and consider creating a new issue to get early feedback on your proposed change.

• Fork the project and create a new branch for your contribution.
• Write your contribution (and any applicable test coverage).
• Make sure all tests pass (bundle exec rake).
• Submit a pull request.