bddfire 2.0.1 → 2.0.2

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: 6392e919e43057fd4d845d80e4fd2b6f70ef73ff
4
- data.tar.gz: b7a340e94ffd768c56b8ed2bec8e7947421e5ff4
3
+ metadata.gz: ffe7a01b873dcefe0ed504afcfa0b9272b3c0dfc
4
+ data.tar.gz: eec84bb9fb2cf28f2d8f4ea86dbd2d4254f288c6
5
5
  SHA512:
6
- metadata.gz: bd8313c1072d27bc8b60e72af79b358124a53d8907eed2fb956d691834fcf98601f5216b8c7ec18c0fc1a84782a658fde5f95f3ace6ae3a319bdcc3c43d7a87b
7
- data.tar.gz: 63bcfb6a7b83a0b1781d096eca87ddd60529a5a402c4f4491336ba30b0c548263c875c169741de84f4b15c6561ee517b36bc5a9c56a7f054d8865040bae28131
6
+ metadata.gz: 3a50d0fc953d3388b0dc6abbe6f9cfcbb1fc534361d70d06d9bbd89a0928e14b00427b76872ba7479e5b07416eb6265e11c262150cfc7d5e9db8e1d7263f54fb
7
+ data.tar.gz: 8a2f9520ff0544b9065dd7e9768419d85f1ad59bac499a006151e0f5908f9a1cf242e33e8d241179a61735d02104fda0d48e4f47111e4a21e583371dd5e9533e
data/README.markdown CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
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. BDDfire can do API testing with RestClient. It also added support for Docker, Gatling, Axe Accessibility Engine
4
4
 
5
- ### BDDfire: Instant Ruby-Cucumber Framework with Docker, Gatling, Accessibility Support
5
+ ### BDDfire: Instant Ruby-Cucumber Framework with Docker, Gatling, Accessibility, REST API Testing Support
6
6
 
7
7
  ## Installation
8
8
 
@@ -52,6 +52,8 @@ BDDfire has inbuilt support for the API Testing. BDDfire uses RestClient to make
52
52
 
53
53
  You can use predefined API Steps [API based](https://github.com/Shashikant86/bddfire/blob/master/pre-defined-steps/rest_api_steps.md)
54
54
 
55
+ ![image](https://github.com/Shashikant86/bddfire-gifs/blob/master/bddfire_api.gif)
56
+
55
57
  ## Load Testing : Gatling
56
58
  You can optionally install Gatling load testing setup.
57
59
 
@@ -141,7 +143,7 @@ You can run your scenarios in Google Chrome
141
143
  $ bundle exec rake api
142
144
 
143
145
 
144
- ![image](https://github.com/Shashikant86/bddfire-gifs/blob/master/bddfire_rest_api.gif)
146
+ ![image](https://github.com/Shashikant86/bddfire-gifs/blob/master/bddfire_api.gif)
145
147
 
146
148
 
147
149
 
@@ -1,3 +1,3 @@
1
1
  module BDDfire
2
- VERSION = '2.0.1'.freeze
2
+ VERSION = '2.0.2'.freeze
3
3
  end
@@ -4,4 +4,4 @@ Feature: Page title
4
4
  Scenario: Check page has title with meaningful text
5
5
  Given I am on the page
6
6
  Then page should have title html attribute with meaningful text
7
- And title attribute shouldn't repeat the content
7
+
@@ -4,7 +4,3 @@ Then(/^page should have title html attribute with meaningful text$/) do
4
4
  puts "======You page title is '#{title}'. We hope it's meaningful===="
5
5
  expect(title).not_to be_empty
6
6
  end
7
-
8
- Then(/^title atttribute shouldn't reapeat the content$/) do
9
- #to do
10
- end
@@ -61,7 +61,7 @@ function run_cucumber_tests {
61
61
  echo "\n Running Bundler"
62
62
  docker exec ${CONTAINER_NAME} bundle install --path vendor/
63
63
  echo "Now running cucumber tests"
64
- docker exec ${CONTAINER_NAME} bundle exec rake poltergeist
64
+ docker exec ${CONTAINER_NAME} bundle exec cucumber -p poltergeist
65
65
  exit $?
66
66
  }
67
67
 
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.1
4
+ version: 2.0.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Shashikant Jagtap
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-04-09 00:00:00.000000000 Z
11
+ date: 2016-04-14 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bundler
@@ -243,7 +243,6 @@ files:
243
243
  - pre-defined-steps/headless_steps.md
244
244
  - pre-defined-steps/rest_api_steps.md
245
245
  - scaffold/accessibility/features/01_validation.feature
246
- - scaffold/accessibility/features/02_javascript.feature
247
246
  - scaffold/accessibility/features/03_language.feature
248
247
  - scaffold/accessibility/features/04_page_titles.feature
249
248
  - scaffold/accessibility/features/05_main_landmark.feature
@@ -1,6 +0,0 @@
1
- @javascript
2
- Feature: JavaScript Feature
3
-
4
- Scenario: JavaScript based scenario
5
- Given I am on the page
6
- Then the core content of the page should be accessible without JavaScrpt and css