cucumber_runner 0.0.4 → 0.0.5

data/.gitignore

@@ -15,3 +15,4 @@ spec/reports
 test/tmp
 test/version_tmp
 tmp
+.idea/

data/README.md

@@ -1,29 +1,45 @@
-# CucumberRunner
+Cucumber_runner
+================
 
-TODO: Write a gem description
+I use cucumber as my main BDD tools on a daily base, no matter on mobile or web. it ease my life very much.
+Running tests for all features is as simple as inputting a single line, however under development phrase,
+especially when I develop scenarios, I need run individual back and forth, so I have to use up and down arrow
+to get correct commands. Programmers are lazy :), so I began to think, what if there's a list of my scenarios,
+and I just can choose any scenarios to run.
 
-## Installation
+Then I wrote cucumber_runner, it's quite simple, it add a formatter to list all features names, categorised by
+feature names, and give each a number, then you choose the number to run.
 
-Add this line to your application's Gemfile:
 
-    gem 'cucumber_runner'
+Install
+========
 
-And then execute:
+Add this line to your application's Gemfile:
+ gem 'cucumber_runner'
 
-    $ bundle
 
 Or install it yourself as:
 
     $ gem install cucumber_runner
 
-## Usage
 
-TODO: Write usage instructions here
+Features
+========
+
+You can use it with zeus or not by providing --user_zeus.
+
+You can pass environment variables as usual.
+
+After running, you can input 's' to stop or simple Ctrl+c, you
+can input 'l' to print the name list again.
+
+
+Contributions
+=============
+Any suggestions, bug reports or feature requests are welcome.
+Any pull requests are very much appreciated.
 
-## Contributing
 
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+License
+============
+MIT License

data/bin/cucumber_runner

@@ -8,7 +8,7 @@ def display_help
           -h, show this help page
           --user_zeus, use zeus or not
 
-          set environment variables, they'll be pass to cucumber as is
+          set environment variables, they'll be pass to cucumber as they are
 
         example:
           cucumber_runner ios_feature --use_zeus
@@ -119,8 +119,10 @@ while input = gets.chomp
 
   case input
 
-    when 'S'
+    when 's'
       exit 0
+    when 'l'
+      get_cucumber_scenario_names
     else
 
       if @@flatten_names.has_key?input

data/lib/cucumber_runner/version.rb

@@ -1,3 +1,3 @@
 module CucumberRunner
-  VERSION = "0.0.4"
+  VERSION = "0.0.5"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cucumber_runner
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.0.5
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-06-11 00:00:00.000000000 Z
+date: 2013-08-26 00:00:00.000000000 Z
 dependencies: []
 description: list cucumber scenarios names, and run them
 email: