bddfire 1.9.8 → 1.9.9

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: b1f394078b63dc1c8bc662b060f3f50cb6e8fb40
4
- data.tar.gz: 388c75bdbf8a5e0d102449c2101bea4242d1ab08
3
+ metadata.gz: fddf7ab996df5e22a6e88da0c0b2155e542cc883
4
+ data.tar.gz: 4df640d0ad2f2d52890389b61bdd26900feffe6d
5
5
  SHA512:
6
- metadata.gz: 922b5480b4017f32d64b151f50c0b17e5a42d7e5e87077c76a8b197c86fde9ca9db979e7f23b4cbb50e05b0c25f1fea8eb752adae5cb9b5009d4a8eef42c4c0e
7
- data.tar.gz: 2702bd41818cf7b559237cfa289f7785f41a6bd69e0d7f6c7648d05013e1e2e420de92f2e820448ee9519496ab5f4dadc86c71e307f08f1c6b79c76dfafad50a
6
+ metadata.gz: 84ffc9b0242115ea6638a2e02d1db2e7031d8b938c35a44ee4e4970db2645d3a00bfb59032eeceea18adaefe3d846a4bf94d643bb832e148786f6f0cab0b7d63
7
+ data.tar.gz: fb23023e7f3089c7901e59de542024a2044fb4eeec7ab16c99f2b682eadae8ccee4da86448b79a2085080dc491063aeaab05ff2142a34963da4812f32f9ac6e9
@@ -1,3 +1,3 @@
1
1
  module BDDfire
2
- VERSION = '1.9.8'.freeze
2
+ VERSION = '1.9.9'.freeze
3
3
  end
@@ -2,7 +2,7 @@ source 'http://rubygems.org'
2
2
  gem 'nokogiri', '1.5.9'
3
3
  gem 'cucumber'
4
4
  gem 'capybara'
5
- gem 'bddfire', '1.9.4'
5
+ gem 'bddfire'
6
6
  gem 'selenium-webdriver'
7
7
  gem 'poltergeist'
8
8
  gem 'rake'
@@ -1,15 +1,67 @@
1
- BDD Scenarios
2
- ========================
1
+ # bddfire
3
2
 
4
- ## Install
3
+ BDDfire: Automate Mobile & Web apps with less code. An instant Ruby-Cucumber BDD framework which supports various popular open-source libraries like Capybara, Selenium-WebDriver, Poltergeist, Relish, Cuke_sniffer, Rubocop, Appium, Saucelabs, Browserstack. Generate default toolkit around BDD with cucumber and friends. It also added support for Docker, Gatling, Axe Accessibility Engine
5
4
 
6
- Your description to install project
5
+ ### ***** BDDfire: Instant Ruby-Cucumber Framework with Docker, Gatling, Accessibility Support************
7
6
 
8
- $ bundle install
9
- Make sure you are using corect ruby version.
7
+ ## Installation
8
+
9
+ Assuming you got Ruby installed. You can run
10
+
11
+ $ gem install bddfire
12
+
13
+ or include it into the Gemfile
14
+
15
+ gem 'bddfire'
10
16
 
11
17
  ## Usage
12
- Now, we need to run bundle install [Fix nokogiri error if you get any by using supported nokogiri version]
18
+
19
+ ### Instant Ruby Cucumber Framework
20
+
21
+ $ bddfire fire_cucumber
22
+
23
+
24
+ This will create 'cucumber' directory and one command will install Ruby Cucumber framework with all possibly supported tools in the 'cucumber' directory. This will create all the directories and files to support following tools
25
+ * Capybara
26
+ * Selenium-Webdriver
27
+ * Poltergeist: PhantomJS based headless driver for capybara
28
+ * Docker support to execute scenarios inside docker containers
29
+ * Run scenarios in parallel 10 processes and rerun failed scenarios.
30
+ * Appium : Mobile test automation Framework
31
+ * Saucelabs : Cloud testing framework
32
+ * Browserstack : Cloud testing framework
33
+ * TestingBot : Cloud testing framework
34
+ * Relish : Living Documentation
35
+ * Yard : Cucumber documentation
36
+ * Rubocop : Ruby code review tool
37
+ * CI Support Script
38
+
39
+ ## Load Testing : Gatling
40
+ You can optionally install Gatling load testing setup.
41
+
42
+ $ bddfire fire_load
43
+ It will setup Load testing environment with gatling. It will create 'load' directory. It's optional but BDDfire will support it to execute your load tests.
44
+
45
+ ## Accessibility Testing : Axe Engine
46
+ You can optionally setup Accessibility Testing setup support Axe Engine
47
+
48
+ $ bddfire fire_accessibility
49
+
50
+ It will setup accessibility frameworks in the 'accessibility' directory. It uses Axe engine to run accessibility tests.
51
+
52
+ ## Docker Support
53
+
54
+ BDDfire allow you execute your cucumber scenarios inside Docker containers. Scenarios with Poltergeist driver can be ran inside containers. One script will do everything for you !
55
+
56
+
57
+ ### Install & Run BDDfire framework
58
+
59
+ Install your skeleton framework with BDDfire
60
+
61
+ $ bddfire fire_cucumber
62
+ $ bddfire fire_load
63
+ $ bddfire fire_accessibility
64
+ Now you should have your framework ready inside 'cucumber' directory. Just install predefine Gems or you can add your own Gems.
13
65
 
14
66
  $ cd cucumber
15
67
  $ bundle install
@@ -17,54 +69,49 @@ Now, we need to run bundle install [Fix nokogiri error if you get any by using s
17
69
  Once installed, you can run cucumber with multiple cabybara driver
18
70
 
19
71
  #Usage
20
- ### Pre-defined-steps
72
+ ## BDDfire Pre-defined-steps
73
+ BDDfire allow us to use predefined steps so that we don't have to write more code while writing cucumber steps. BDDfire has following predefined steps which can be used anytime during your project.
74
+
75
+ ### Browser Based Pre-defined-steps
76
+
21
77
  You can use[Browser based](https://github.com/Shashikant86/bddfire/blob/master/pre-defined-steps/capybara_steps.md) steps
78
+
79
+ ### Poltergeist Based Pre-defined-steps
22
80
  You can use headless Poltergeist based [headless Poltergeist based](https://github.com/Shashikant86/bddfire/blob/master/pre-defined-steps/headless_steps.md) steps
23
81
 
82
+ ### Accessibility related Pre-defined-steps
83
+
84
+ You can also use [Accessibility steps](https://github.com/Shashikant86/bddfire/blob/major-refactor/pre-defined-steps/accessibility_steps.md)
85
+
24
86
  ### Parallel Cucumber & Re-run Failed
87
+
25
88
  You can run entire test suite in 10 different processes but you can increase number of processes. The reports are generated for each process. If any scenario failed it will re-run. It will use poltergeist by default but you can change in Rakefile
26
89
 
27
- $ rake parallel_cucumber
90
+ $ bundle exec rake parallel_cucumber
28
91
 
29
- ###Selenium Firefox
92
+ ### Selenium Firefox
30
93
  You can use selenium driver to run scenario in browser [firefox].
31
94
 
32
- $ rake selenium
33
-
34
- You can run cucumber with profile like this
35
-
36
- $ bundle exec cucumber -p selenium
95
+ $ bundle exec rake selenium
37
96
 
38
97
  ###Headless Poletergeist
39
98
  You can use PhantomJS based Capybara driver Poltergeist driver.
40
99
 
41
-
42
- You can run cucumber with profile like this
43
-
44
- $ bundle exec cucumber -p poltergeist
45
-
46
- OR
47
-
48
- $ rake poltergeist
100
+ $ bundle exec rake poltergeist
49
101
 
50
102
  ###Chrome Driver
51
103
  You can run your scenarios in Google Chrome
52
104
 
53
- $ rake chrome
54
- You can run cucumber with profile like this
55
-
56
- $ bundle exec cucumber -p chrome
57
-
105
+ $ bundle exec rake chrome
58
106
 
59
107
  ###Cloud Testing Frameworks
60
108
  Please enter your USERNAME and KEY in the env.rb file
61
109
 
62
- $ rake sauce/browserstack/testingbot
63
- OR
110
+ $ bundle exec rake sauce/browserstack/testingbot
64
111
 
65
- $ bundle exec cucumber -p sauce/browserstack/testingbot
66
112
 
67
113
  ###Appium:
114
+
68
115
  Run Appium server in the background.
69
116
 
70
117
  $ npm install
@@ -82,6 +129,7 @@ OR
82
129
  $ bundle exec cucumber -p appium
83
130
 
84
131
  ###Cuke_sniffer
132
+
85
133
  You can use cuke_sniffer to detect smells in your Cucumber. It will generate reports in the cuke_sniffer.html in the 'reports' directory.
86
134
 
87
135
  $ rake cuke_sniffer
@@ -91,12 +139,29 @@ You can use cuke_sniffer to detect smells in your Cucumber. It will generate rep
91
139
  You can use rubocop to detect ruby errors in your Ruby file
92
140
 
93
141
  $ rake rubocop
142
+
94
143
  This will report all the offence in rubocop.
95
144
 
96
- ## CI Integration
97
145
 
98
- Currently, you can use the script 'ci_script' on Jenkins or Hudson. More CI Integration is on the way.
146
+ ## Docker
147
+
148
+ We can run our cucumber scenario inside Docker containers. Assuming you have Docker installed. Check your Docker installation before using.
149
+
150
+ $ bundle exec rake docker
151
+ This will build Docker image 'bddfire-ci' and run cucumber scenarios inside container 'bddfire-ci'.
152
+
153
+ ## Gatling
154
+
155
+ You can use Gatling setup to execute load tests against your endpoints. Simply change 'load/user-files/simulation/SampleLoadTEST.scala' file and puts your URL to Test as base URL.
156
+
157
+ $ cd load
158
+ $ sh gatling_local.sh
159
+ This will run load tests against your url. You are free to record new simulations. Once finished there will be link to HTML report at the end.
160
+
161
+ There is CI integration to plug it with jenkins.
162
+
163
+ ## Accessibility Testing : Axe
99
164
 
100
- You need pass rake rask to the script
165
+ We can run accessibility checks on our web page using BDDfire. You have to pass URL as environment variable e.g
101
166
 
102
- $ ./ci_script parallel_cucumber
167
+ $ bundle exec cucumber accessibility/features URL="http://www.google.co.uk"
@@ -64,8 +64,6 @@ Cucumber::Rake::Task.new(:testingbot) do |t|
64
64
  end
65
65
 
66
66
  Cucumber::Rake::Task.new(:appium) do |t|
67
- puts '===== Make sure you have started Appium server in the background====='
68
- puts '===== You can start it with rake task start_appium ....====='
69
67
  t.cucumber_opts = "features -p appium_android_web ADB_SERIAL=#{ADB_SERIAL} --format pretty --profile html "
70
68
  end
71
69
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bddfire
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.9.8
4
+ version: 1.9.9
5
5
  platform: ruby
6
6
  authors:
7
7
  - Shashikant Jagtap
@@ -185,7 +185,7 @@ files:
185
185
  - features/support/env.rb
186
186
  - features/support/support_code.rb
187
187
  - lib/bddfire.rb
188
- - lib/bddfire/accesibility/axe.rb
188
+ - lib/bddfire/accessibility/axe.rb
189
189
  - lib/bddfire/assertions/assert.rb
190
190
  - lib/bddfire/mobile/mobile_methods.rb
191
191
  - lib/bddfire/mobile/mobile_steps.rb