You're looking at a past competition year · Check out the latest Rails Rumble »

Launch Site MutationStation

This is an entry in the 2015 Rails Rumble. After checking it out, we encourage you
to leave feedback and then take a look at the hundreds of other amazing entries.

V200_team-137

Description

Filed in Developer Tools.

MutationStation is a tool that evaluates the strength of RSpec tests in a Ruby application. It can be used on personal projects, or as a way to find meaningful areas to contribute to open source projects.

Built By Team "TinderBox"

Built With

Interested in seeing what was used to build this application? Resources may include things like open source libraries, third party APIs, and icons.

The awesome mutant-rspec gem was forked and modified extensively to support MutationStation. Changes can be viewed here: https://github.com/jheth/mutant/tree/json-output-reporter

We used Bootstrap with the Flatly theme ...

Read More...

The awesome mutant-rspec gem was forked and modified extensively to support MutationStation. Changes can be viewed here: https://github.com/jheth/mutant/tree/json-output-reporter

We used Bootstrap with the Flatly theme from Bootswatch for a large portion of the front end. We also took advantage of Font-Awesome, select2, typeahead.js and toastr. high_voltage from thoughtbot was used for the static landing page.

We used devise w/ omniauth-github for authentication. Ocktokit for interacting with the GitHub api, pusher for delivering live updates to the application, kaminari and ransack for pagination and searching, slim as an alternative to ERB, delayed_job for background processing, rspec, shoulda-matchers and factory_girl for testing, pry and awesome-print for debugging, breadcrumbs_on_rails and, of course, the mutant-rspec gem!

Using sendgrid for email delivery upon account creation and build completion.

Heavy reliance on gem bundler as we are cloning, bundling, and running the mutant-rspec process over submitted repositories. We dynamically inject the mutant-rspec (determining v2 vs v3) into the user's Gemfile to avoid any code changes.

comments powered by Disqus