README.md in torm-0.2.0 vs README.md in torm-0.2.1

@@ -75,10 +75,18 @@
   * On equal policy level, more specific rules (more conditions) overrule less specific ones. Rationale: "We usually don't do this, except when it's summer."
 * Decisions take a rule and a bunch of environment conditions
   * We gather all rules, then filter irrelevant rules based on environment conditions
   * Because rules are stored in order of priority, the first rule remaining is the one that applies the best.
 
+## Development / testing
+
+This project uses minitest. Local development:
+
+* Checkout the project
+* `bundle install` to install all development gems.
+* `rake test` to run the tests.
+
 ## Versioning
 
 Torm tries to follow Semantic Versioning 2.0.0, this means that given a version number MAJOR.MINOR.PATCH, it will increment the:
 
 * MAJOR version when you make incompatible API changes,
@@ -90,8 +98,9 @@
 
 ## Contributing
 
 1. Fork it ( https://github.com/narnach/torm/fork )
 2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create a new Pull Request
+3. Write code. Don't forget to write tests and run all tests!
+4. Commit your changes (`git commit -am 'Add some feature'`)
+5. Push to the branch (`git push origin my-new-feature`)
+6. Create a new Pull Request