cucumber_runner 0.0.4 → 0.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/.gitignore +1 -0
- data/README.md +31 -15
- data/bin/cucumber_runner +4 -2
- data/lib/cucumber_runner/version.rb +1 -1
- metadata +2 -2
data/.gitignore
CHANGED
data/README.md
CHANGED
@@ -1,29 +1,45 @@
|
|
1
|
-
|
1
|
+
Cucumber_runner
|
2
|
+
================
|
2
3
|
|
3
|
-
|
4
|
+
I use cucumber as my main BDD tools on a daily base, no matter on mobile or web. it ease my life very much.
|
5
|
+
Running tests for all features is as simple as inputting a single line, however under development phrase,
|
6
|
+
especially when I develop scenarios, I need run individual back and forth, so I have to use up and down arrow
|
7
|
+
to get correct commands. Programmers are lazy :), so I began to think, what if there's a list of my scenarios,
|
8
|
+
and I just can choose any scenarios to run.
|
4
9
|
|
5
|
-
|
10
|
+
Then I wrote cucumber_runner, it's quite simple, it add a formatter to list all features names, categorised by
|
11
|
+
feature names, and give each a number, then you choose the number to run.
|
6
12
|
|
7
|
-
Add this line to your application's Gemfile:
|
8
13
|
|
9
|
-
|
14
|
+
Install
|
15
|
+
========
|
10
16
|
|
11
|
-
|
17
|
+
Add this line to your application's Gemfile:
|
18
|
+
gem 'cucumber_runner'
|
12
19
|
|
13
|
-
$ bundle
|
14
20
|
|
15
21
|
Or install it yourself as:
|
16
22
|
|
17
23
|
$ gem install cucumber_runner
|
18
24
|
|
19
|
-
## Usage
|
20
25
|
|
21
|
-
|
26
|
+
Features
|
27
|
+
========
|
28
|
+
|
29
|
+
You can use it with zeus or not by providing --user_zeus.
|
30
|
+
|
31
|
+
You can pass environment variables as usual.
|
32
|
+
|
33
|
+
After running, you can input 's' to stop or simple Ctrl+c, you
|
34
|
+
can input 'l' to print the name list again.
|
35
|
+
|
36
|
+
|
37
|
+
Contributions
|
38
|
+
=============
|
39
|
+
Any suggestions, bug reports or feature requests are welcome.
|
40
|
+
Any pull requests are very much appreciated.
|
22
41
|
|
23
|
-
## Contributing
|
24
42
|
|
25
|
-
|
26
|
-
|
27
|
-
|
28
|
-
4. Push to the branch (`git push origin my-new-feature`)
|
29
|
-
5. Create new Pull Request
|
43
|
+
License
|
44
|
+
============
|
45
|
+
MIT License
|
data/bin/cucumber_runner
CHANGED
@@ -8,7 +8,7 @@ def display_help
|
|
8
8
|
-h, show this help page
|
9
9
|
--user_zeus, use zeus or not
|
10
10
|
|
11
|
-
set environment variables, they'll be pass to cucumber as
|
11
|
+
set environment variables, they'll be pass to cucumber as they are
|
12
12
|
|
13
13
|
example:
|
14
14
|
cucumber_runner ios_feature --use_zeus
|
@@ -119,8 +119,10 @@ while input = gets.chomp
|
|
119
119
|
|
120
120
|
case input
|
121
121
|
|
122
|
-
when '
|
122
|
+
when 's'
|
123
123
|
exit 0
|
124
|
+
when 'l'
|
125
|
+
get_cucumber_scenario_names
|
124
126
|
else
|
125
127
|
|
126
128
|
if @@flatten_names.has_key?input
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: cucumber_runner
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.5
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2013-
|
12
|
+
date: 2013-08-26 00:00:00.000000000 Z
|
13
13
|
dependencies: []
|
14
14
|
description: list cucumber scenarios names, and run them
|
15
15
|
email:
|