cukedep 0.0.4 → 0.0.5

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    OTMxMmVkZTNiMjA0ZDM2MjQwZDcyM2QxMzJjZGJkNjFhNDE2NjAwNg==
+    YzA2NDcyMDk3YzZkNmY0ZTkxYWM4MjViODhkNmRiNDYyMTM0NjE4Yw==
   data.tar.gz: !binary |-
-    OGRlYzE2NDBhYzdkZDg4NWUwZWNkNTEzOTFkYzdiYTdiYmMyYzQ2Nw==
+    M2Q5NmI0NzgzMTVhMWFkNmNkN2MwOTM5NDNhZTczMTdlYTFiMTBlMQ==
 !binary "U0hBNTEy":
   metadata.gz: !binary |-
-    ZTg5NmEwZGZmNzEwZmM0YTgzODIxYzhjZjliNzg3ZmE5MTQyZmMxYWM2N2Q2
-    NjVlNTNlOTc3NDk2YWE5N2UwNWRmZDgwMmI1OWNhYWNiMTEzOTUxYzllZTQ5
-    ZmVjZDljODU0NDg3NzZiMzdkZWIxNzFlYjU1NWY0MjkzYjkwNGM=
+    ODM5NjBjZjdkYjE5ZjQ4ZmE0OTQ2ODJlNjMzNWQ1OTU4MTAyOGJjYmI3MmVi
+    MzUzZTUwOTY3YjgzNTRlODZmZTMxMTI5NDg2MjE0NWY2YjM2MWFhZWI2MGJj
+    YWRhOGVkMWMyMGNhMzFhMTcwNTY2ZTcyN2Y2ZGRhMTVmZjgxY2M=
   data.tar.gz: !binary |-
-    NmFmNzRjYTZlMTc3MmQ3OTIwMTE2MTJmYTY1MjA1M2NkODM4Y2Q3ZWQ3ZTZi
-    MTQ3ZjhmNjBmOWQzZGQzMTRlYzdiZDFhZDJmYTMzNjJhY2VjZjY3MjFlNWU5
-    ZDkxMDI5OTEwMmRiNzBkYjZiY2ViYWUzZDA4YjAyNzlhMTZlYjA=
+    MzM3NmFiNTY1MjNjM2U5MDk0ZmVlM2EyMWNlZTc3MTExNWNmYzJiZDgzZDY0
+    MjlhYzdmNTk2NzE2YWVhZWFiNmQwZTQ2YWVmMjRhMTRjYmY1MWQ0ZGIzNTA5
+    M2QzYjMzYTY5OTIwYjJmMGExMDg1M2RhOTRkYzk3NTAzYzgwMzU=

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+### 0.0.5 / 2013-10-24
+* [CHANGE] Files `README.md` Added section on how to specify dependencies.
+
 ### 0.0.4 / 2013-10-24
 * [CHANGE] Files `Gemfile`, `cukedep.gemspec`. Updated dependencies towards other gems.
 

data/README.md

@@ -47,7 +47,7 @@ Stay in that folder and type the following command-line:
 cukedep --project ../../../sample --dry-run
 ```
 
-You instructed cukedep to do the following:
+You told cukedep to do the following:
 * Read (parse) all the feature files in the current dir.
 * Resolve the dependencies between the feature files (based on Gherkin @tags with a special format).
 * Generate a number of dependency reports and drawing.
@@ -57,10 +57,40 @@ the project located at the relative path ```../../../sample```
 To generate all the above files and run the feature files with Cucumber,
 then retry the command line without the --dry-run option:
 ```bash  
-cukedep --project ../../../sample --dry-run
+cukedep --project ../../../sample
+```
+
+Now you see cukedep redoing the same actions as previously but in addition
+it:
+* Copies a feature file from the current directive to the Cucumber-based project
+* Let Cucumber execute the feature file
+* Repeat the two above steps in a sequence that meet the dependencies specified in the feature files.
+
+
+### How can I define dependencies? ###
+To define dependencies between feature files, use Gherkin specific tags.
+Suppose that feature `foo` depends on feature `bar`.
+Then the feature file `foo` may begin as follows:
+
+```cucumber
+# The next line names this feature 'foo' and make dependent on 'bar'
+@feature:foo @depends_on:bar
+Feature: Check-in
+  As a video rental employee
+  I want to register return of rented videos
+  So that other members can them too  
+```
+
+While feature `bar` may start like this:
+```cucumber
+# The next line names this feature 'bar'
+@feature:bar
+Feature: Renting videos
+  As a video rental employee
+  I want to register rentals made by a member 
+  So I can run my business
 ```
 
-### How can I define ###
 
 
 Copyright

data/lib/cukedep/constants.rb

@@ -3,7 +3,7 @@
 
 module Cukedep # Module used as a namespace
   # The version number of the gem.
-  Version = '0.0.4'
+  Version = '0.0.5'
 
   # Brief description of the gem.
   Description = 'Manage dependencies between Cucumber feature files'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cukedep
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.0.5
 platform: ruby
 authors:
 - Dimitri Geshef