bddfire 1.5.7 → 1.5.8
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 +8 -8
- data/README.markdown +28 -24
- data/lib/bddfire/version.rb +1 -1
- data/scaffold/features/support/env.rb +10 -7
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,15 +1,15 @@
|
|
1
1
|
---
|
2
2
|
!binary "U0hBMQ==":
|
3
3
|
metadata.gz: !binary |-
|
4
|
-
|
4
|
+
ODYwZDIwMjQ1NWNiMzI4OWMzMWU2MDZjZmE0N2QyMzk1NDA5M2JkZA==
|
5
5
|
data.tar.gz: !binary |-
|
6
|
-
|
6
|
+
ZTcyNzU0YzZiMmMxY2UwZjQ0ZDc0OWMwZjc3ZDkwNzc4ZTU0ZGI0Yg==
|
7
7
|
SHA512:
|
8
8
|
metadata.gz: !binary |-
|
9
|
-
|
10
|
-
|
11
|
-
|
9
|
+
NDI1NTJkY2ZjZmI2MGQxNmQ4MWJkMzZlOWI3ZTg0ZTkxMjM5NjMzZjE2NzUw
|
10
|
+
MjFjNWYzNGJjNjNiNWIwYWI0ZjU3M2Q1NjQ1NzM3ZmE1ODcxNmNjZGU4MjJh
|
11
|
+
ZmFmM2E3Y2NjMmMwNDMwODBmMmU3ZDlmN2EyMTMyYmFkNTc2ZjY=
|
12
12
|
data.tar.gz: !binary |-
|
13
|
-
|
14
|
-
|
15
|
-
|
13
|
+
MTE3MmNlMTc2ZDUwZTNmMmY4MTUzYmJiZGViY2RkMTkwMjg4YzBmYzU5NGJh
|
14
|
+
NGUzMGU2NzZkMDZiM2RjMmJlYjYyZWEwYTRhNjNmMDE2NDg5ZGI1OTY4MWY4
|
15
|
+
MTE4NDRjZWU2OTViNTE3MWRlZmFkOWM5ZjAwYmQzZjZjM2RmMmY=
|
data/README.markdown
CHANGED
@@ -6,7 +6,7 @@ Generate default toolkit around BDD with cucumber and friends
|
|
6
6
|
The usual:
|
7
7
|
|
8
8
|
$ gem install bddfire
|
9
|
-
|
9
|
+
|
10
10
|
or include it into the Gemfile
|
11
11
|
|
12
12
|
gem 'bddfire'
|
@@ -68,59 +68,63 @@ Now, we need to run bundle install [Fix nokogiri error if you get any by using s
|
|
68
68
|
|
69
69
|
$ bundle install
|
70
70
|
|
71
|
-
Once installed, you can run cucumber with multiple caybara driver
|
71
|
+
Once installed, you can run cucumber with multiple caybara driver
|
72
|
+
|
73
|
+
Use Selenium
|
72
74
|
|
73
|
-
|
75
|
+
$ bundle exec cucumber -p selenium
|
74
76
|
|
75
|
-
|
77
|
+
Use Headless Poletergeist
|
76
78
|
|
77
|
-
Use Headless Poletergeist
|
78
|
-
|
79
79
|
$ bundle exec cucumber -p poltergeist
|
80
80
|
|
81
|
-
Use Saucelabs : Please enter your SAUCE_USERNAME and SAUCELABS key in the env.rb file
|
81
|
+
Use Saucelabs : Please enter your SAUCE_USERNAME and SAUCELABS key in the env.rb file
|
82
82
|
|
83
|
-
$ bundle exec cucumber -p sauce
|
84
|
-
|
85
|
-
Use Browserstack : Please enter your BS_USERNAME and BS_KEY key in the env.rb file
|
83
|
+
$ bundle exec cucumber -p sauce
|
84
|
+
|
85
|
+
Use Browserstack : Please enter your BS_USERNAME and BS_KEY key in the env.rb file
|
86
86
|
|
87
87
|
$ bundle exec cucumber -p browserstak
|
88
88
|
|
89
|
-
Use TestingBot : Please enter your TB_KEY and TB_SECRET key in the env.rb file
|
89
|
+
Use TestingBot : Please enter your TB_KEY and TB_SECRET key in the env.rb file
|
90
90
|
|
91
91
|
$ bundle exec cucumber -p testingbot
|
92
92
|
|
93
|
-
Using Appium, run Appium server in the background. You need to have iOS setup.
|
93
|
+
Using Appium, run Appium server in the background. You need to have iOS setup.
|
94
94
|
|
95
|
-
$ npm install
|
95
|
+
$ npm install
|
96
96
|
$ ./node_modules/.bin/appium
|
97
97
|
|
98
|
-
Now run cucumber with appium
|
99
|
-
|
100
|
-
$ bundle exec cucumber -p
|
101
|
-
|
102
|
-
|
98
|
+
Now run cucumber with appium andriod
|
99
|
+
|
100
|
+
$ bundle exec cucumber -p appium_android ADB_SERIAL=serial_number
|
101
|
+
|
102
|
+
Now run cucumber with appium iOS
|
103
|
+
|
104
|
+
$ bundle exec cucumber -p appium_ios
|
105
|
+
|
106
|
+
## Use Rake
|
103
107
|
|
104
108
|
You can also use Rake taks created automatically for you
|
105
109
|
|
106
110
|
$ bundle exec rake features
|
107
|
-
|
108
|
-
You can run Cuke_sniffer report on your project
|
111
|
+
|
112
|
+
You can run Cuke_sniffer report on your project
|
109
113
|
|
110
114
|
$ bundle exec rake cuke_sniffer
|
111
115
|
|
112
|
-
You can run rubocop report on your project
|
116
|
+
You can run rubocop report on your project
|
113
117
|
|
114
118
|
$ bundle exec rake rubocop
|
115
119
|
|
116
120
|
|
117
121
|
## CI Integration
|
118
122
|
|
119
|
-
Currently, you can use the script 'ci_script' on Jenkins or Hudson. More CI inegration is on the way.
|
123
|
+
Currently, you can use the script 'ci_script' on Jenkins or Hudson. More CI inegration is on the way.
|
120
124
|
|
121
|
-
You need pass rake rask to the script
|
125
|
+
You need pass rake rask to the script
|
122
126
|
|
123
|
-
$ ./ci_script features
|
127
|
+
$ ./ci_script features
|
124
128
|
|
125
129
|
|
126
130
|
## Awesome and more awesome stuff is coming soon. STAY TUNED !
|
data/lib/bddfire/version.rb
CHANGED
@@ -92,13 +92,16 @@ Capybara.register_driver :sauce do |app|
|
|
92
92
|
:url => "http://SAUCE_USERNAME:SAUCE_API_KEY@ondemand.saucelabs.com:80/wd/hub")
|
93
93
|
end
|
94
94
|
|
95
|
-
Capybara.register_driver :
|
96
|
-
|
97
|
-
|
98
|
-
|
99
|
-
|
100
|
-
|
101
|
-
|
95
|
+
Capybara.register_driver :appium_android do |app|
|
96
|
+
capabilities = {:platformName => 'Android', :deviceName => 'android', :browserName => 'Chrome', :uuid => ENV['ADB_SERIAL']}
|
97
|
+
Capybara::Selenium::Driver.new(app,
|
98
|
+
:browser => :remote,
|
99
|
+
:desired_capabilities => capabilities,
|
100
|
+
:url => "http://0.0.0.0:4723/wd/hub")
|
101
|
+
end
|
102
|
+
|
103
|
+
Capybara.register_driver :appium_ios do |app|
|
104
|
+
capabilities = {:platform => 'Mac', :browserName => 'iOS', :version => '6.0'}
|
102
105
|
Capybara::Selenium::Driver.new(app,
|
103
106
|
:browser => :remote,
|
104
107
|
:desired_capabilities => capabilities,
|
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: 1.5.
|
4
|
+
version: 1.5.8
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Shashikant Jagtap
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2014-
|
11
|
+
date: 2014-10-14 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: thor
|