README.md in cucumber_priority-0.1.2 vs README.md in cucumber_priority-0.2.0
- old
+ new
@@ -1,8 +1,11 @@
-cucumber_priority - overridable step definitions for Cucumber
-=============================================================
+cucumber_priority [](https://travis-ci.org/makandra/cucumber_priority)
+=================
+Overridable step definitions for Cucumber
+-----------------------------------------
+
[Cucumber](https://github.com/cucumber/cucumber-ruby) raises an error if more than one step definitions match a step.
This gem provides a way to mark step definitions as *overridable*, meaning that they can always be overshadowed by a more specific version without raising an error.
@@ -46,11 +49,11 @@
Supported Cucumber versions
----------------------------
-cucumber_priority is tested against Cucumber 1.2, 1.3 and 2.1.
+cucumber_priority is tested against Cucumber 1.3, 2.4 and 3.0.
Installation
------------
@@ -62,13 +65,21 @@
Development
-----------
-- We run tests against several Cucumber versions.
-- You can bundle all versions with `rake all:install`.
-- You can run specs against all versions with `rake all:spec`.
-See `spec/support/database.sample.yml` for an example.
+There are tests in `spec`. We only accept PRs with tests. To run tests:
+
+- Install Ruby 2.3.3
+- Install development dependencies using `bundle install`
+- Run tests using `bundle exec rspec`
+
+We recommend to test large changes against multiple versions of Ruby and multiple dependency sets. Supported combinations are configured in `.travis.yml`. We provide some rake tasks to help with this:
+
+- Install development dependencies using `bundle matrix:install`
+- Run tests using `bundle matrix:spec`
+
+Note that we have configured Travis CI to automatically run tests in all supported Ruby versions and dependency sets after each push. We will only merge pull requests after a green Travis build.
If you would like to contribute:
- Fork the repository.
- Push your changes **with passing specs**.