README.md in cogy-0.5.2 vs README.md in cogy-0.6.0

- old
+ new

@@ -73,11 +73,11 @@ ## Requirements * Cog 1.0.0.beta2 or later * [cogy bundle](https://github.com/skroutz/cogy-bundle) 0.4.0 or later * Ruby 2.1 or later -* Rails 4.2 (support for Rails 5 is on the way) +* Rails 4.2 or later ## Status Cogy is still in public alpha. @@ -257,11 +257,11 @@ # a string. # # Default: "0.0.1" version: "0.0.1", - # if you used a callable object, it will be evaluated each time the inventory + # If you used a callable object, it will be evaluated each time the inventory # is called. This can be useful if you want the version to change # automatically. # # For example, this will change the version only when a command is # added or is modified (uses the 'grit' gem). @@ -355,14 +355,21 @@ `app/views/cogy/error.text.erb`. ## Testing commands We don't yet provide means to write tests for the commands, but you can easily -test them by executing a request to your development server: +test them by executing a request to your development server. For example, +if you mounted the engine like so: +```ruby +mount Cogy::Engine, at: "cogy" +``` + +you can test a `foo` command like this: + ```shell -$ curl -XPOST --data "COG_ARGV_0=foo" http://localhost:3000/cogy/foo +$ curl -XPOST --data "COG_ARGV_0=foo" http://localhost:3000/cogy/cmd/foo ``` In the request body you may pass the complete or any part of the [Cog environment](https://cog-book.operable.io/#_command_environment_variables) you need. @@ -448,11 +455,11 @@ See [_Deployment_](#deployment) on information about how this trigger is invoked. ## Development -Running the tests and RuboCop: +Running the tests and RuboCop for the latest Rails version: ```shell $ rake ``` @@ -470,9 +477,22 @@ Generating documentation: ```shell $ rake yard +``` + +Running the tests for all the supported Rails versions: + + +```shell +$ appraisal rake +``` + +Or for a specific version: + +```shell +$ appraisal 4.2 rake test ``` ## Authors * [Agis Anastasopoulos](https://github.com/agis-)