bddfire 2.0.6 → 2.0.7
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.
- checksums.yaml +4 -4
- data/Gemfile.lock +2 -2
- data/features/bddfire_cli.feature +2 -9
- data/features/install.feature +6 -5
- data/lib/bddfire/version.rb +1 -1
- data/scaffold/config_files/Rakefile +4 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 50b64bcfea3928414db745103bef093eb067352c
|
|
4
|
+
data.tar.gz: ef82e40a2283d2013e5df213a5b7f5fc30fe9306
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 875e880cca89ca553c5f6ead3941d0d5e6dd01feb828b5ccf9147404b2d1f74edc19636a1d864cc7aa88bafeb16550568476cc50cbda1a4996f2eecffe3dd011
|
|
7
|
+
data.tar.gz: 78ab7cb71d4487282decb5b9e67ed5e46ade53b2772063a669269d9616455968a5bf0efb34de0866499ec996c3cde6f8c29ba70a9e0d3c07daf9919ed8b40043
|
data/Gemfile.lock
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
bddfire (2.0.
|
|
4
|
+
bddfire (2.0.6)
|
|
5
5
|
axe-matchers
|
|
6
6
|
be_valid_asset
|
|
7
7
|
bundler
|
|
@@ -193,7 +193,7 @@ GEM
|
|
|
193
193
|
websocket-extensions (0.1.2)
|
|
194
194
|
xpath (2.0.0)
|
|
195
195
|
nokogiri (~> 1.3)
|
|
196
|
-
yard (0.9.
|
|
196
|
+
yard (0.9.6)
|
|
197
197
|
yard-cucumber (3.1.0)
|
|
198
198
|
cucumber (~> 2)
|
|
199
199
|
gherkin (~> 4.0)
|
|
@@ -1,16 +1,9 @@
|
|
|
1
|
-
Feature: Install bddfire
|
|
1
|
+
Feature: Install bddfire
|
|
2
2
|
|
|
3
3
|
|
|
4
|
-
Scenario: Print version
|
|
5
|
-
Given I successfully run `bddfire version`
|
|
6
|
-
Then output should be
|
|
7
|
-
"""
|
|
8
|
-
2.0.4
|
|
9
|
-
"""
|
|
10
|
-
|
|
11
4
|
Scenario: Using rubygems
|
|
12
5
|
Given I successfully run `bddfire`
|
|
13
6
|
Then the output should contain:
|
|
14
7
|
"""
|
|
15
8
|
Usage: bddfire <command-name> [parameters] [options]
|
|
16
|
-
"""
|
|
9
|
+
"""
|
data/features/install.feature
CHANGED
|
@@ -1,8 +1,9 @@
|
|
|
1
|
-
Feature: Install bddfire
|
|
1
|
+
Feature: Install bddfire
|
|
2
2
|
|
|
3
3
|
|
|
4
4
|
Scenario: Using rubygems
|
|
5
|
-
Given I successfully run `gem
|
|
6
|
-
Then
|
|
7
|
-
|
|
8
|
-
|
|
5
|
+
Given I successfully run `gem list | bddfire`
|
|
6
|
+
Then the output should contain:
|
|
7
|
+
"""
|
|
8
|
+
bddfire
|
|
9
|
+
"""
|
data/lib/bddfire/version.rb
CHANGED
|
@@ -43,6 +43,10 @@ Cucumber::Rake::Task.new(:selenium) do |t|
|
|
|
43
43
|
t.cucumber_opts = 'features -p selenium --format pretty --profile html -t ~@api '
|
|
44
44
|
end
|
|
45
45
|
|
|
46
|
+
Cucumber::Rake::Task.new(:firefox) do |t|
|
|
47
|
+
t.cucumber_opts = 'features -p selenium --format pretty --profile html -t ~@api '
|
|
48
|
+
end
|
|
49
|
+
|
|
46
50
|
Cucumber::Rake::Task.new(:poltergeist) do |t|
|
|
47
51
|
t.cucumber_opts = 'features -p poltergeist --format pretty --profile html -t ~@api '
|
|
48
52
|
end
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: bddfire
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 2.0.
|
|
4
|
+
version: 2.0.7
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Shashikant Jagtap
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2017-01-
|
|
11
|
+
date: 2017-01-10 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: bundler
|