Sha256: ec3a09a9724f3178a71135561ae18198f42aea4c08337ae483b1f17d036c3004
Contents?: true
Size: 1.06 KB
Versions: 11
Compression:
Stored size: 1.06 KB
Contents
#Contributing to ![Flapjack](https://raw.github.com/flapjack/flapjack/gh-pages/images/flapjack-2013-notext-transparent-50-50.png "Flapjack") Flapjack [![Build Status](https://travis-ci.org/flapjack/flapjack.png)](https://travis-ci.org/flapjack/flapjack) Please see the [Contributing to Flapjack](https://github.com/flapjack/flapjack/wiki/DEVELOPING) section of the Flapjack wiki. > Flapjack is, and will continue to be, well tested. Monitoring is like continuous integration for production apps, so why shouldn't your monitoring system have tests? ## Quick Start 1. clone the repo git clone https://github.com/flapjack/flapjack.git 2. install development dependencies with bundler: cd flapjack gem install bundler bundle install 3. install redis 4. run unit tests rake spec 5. run integration tests rake features 6. code coverage for tests COVERAGE=x rake spec COVERAGE=x rake features 7. make changes with tests, send a [pull request](https://help.github.com/articles/creating-a-pull-request), share love!
Version data entries
11 entries across 11 versions & 1 rubygems