selenium_fury 0.5.11 → 0.5.12

Sign up to get free protection for your applications and to get access to all the features.
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.5.11
1
+ 0.5.12
@@ -10,8 +10,10 @@ module SeleniumFury
10
10
  end
11
11
 
12
12
  def validate(page_object, *live_url)
13
- unless browser.nil?
14
- return check_page_file_class(page_object,*live_url)
13
+ if defined?(browser)
14
+ unless browser.nil?
15
+ return check_page_file_class(page_object, *live_url)
16
+ end
15
17
  end
16
18
  unless driver.nil?
17
19
  return web_driver_validate(page_object)
@@ -5,11 +5,11 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = "selenium_fury"
8
- s.version = "0.5.11"
8
+ s.version = "0.5.12"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Scott Sims", "Tim Tischler"]
12
- s.date = "2012-05-01"
12
+ s.date = "2012-06-27"
13
13
  s.description = "Generate and validate page objects with this page object factory for Selenium."
14
14
  s.email = "ssims98@gmail.com"
15
15
  s.extra_rdoc_files = [
@@ -67,7 +67,7 @@ Gem::Specification.new do |s|
67
67
  ]
68
68
  s.homepage = "https://github.com/scottcsims/SeleniumFury"
69
69
  s.require_paths = ["lib"]
70
- s.rubygems_version = "1.8.21"
70
+ s.rubygems_version = "1.8.24"
71
71
  s.summary = "Selenium Fury allows an automated tester to quickly build page files to use in the page object pattern. Each page file represents a page under test with attributes of all the locators selenium needs to run tests on the page and methods that represent actions that can be performed on the page. You use the generator to build the page files. After the page has been updated you can use the validator to go through all of the selenium locators you are using in your page file and return a list of the locators that it could not find. If there are missing locators you can then rerun the generator to generate new selenium locators for your page. http://www.scottcsims.com"
72
72
 
73
73
  if s.respond_to? :specification_version then
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: selenium_fury
3
3
  version: !ruby/object:Gem::Version
4
- hash: 29
4
+ hash: 19
5
5
  prerelease:
6
6
  segments:
7
7
  - 0
8
8
  - 5
9
- - 11
10
- version: 0.5.11
9
+ - 12
10
+ version: 0.5.12
11
11
  platform: ruby
12
12
  authors:
13
13
  - Scott Sims
@@ -16,7 +16,7 @@ autorequire:
16
16
  bindir: bin
17
17
  cert_chain: []
18
18
 
19
- date: 2012-05-01 00:00:00 Z
19
+ date: 2012-06-27 00:00:00 Z
20
20
  dependencies:
21
21
  - !ruby/object:Gem::Dependency
22
22
  type: :runtime
@@ -274,7 +274,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
274
274
  requirements: []
275
275
 
276
276
  rubyforge_project:
277
- rubygems_version: 1.8.21
277
+ rubygems_version: 1.8.24
278
278
  signing_key:
279
279
  specification_version: 3
280
280
  summary: Selenium Fury allows an automated tester to quickly build page files to use in the page object pattern. Each page file represents a page under test with attributes of all the locators selenium needs to run tests on the page and methods that represent actions that can be performed on the page. You use the generator to build the page files. After the page has been updated you can use the validator to go through all of the selenium locators you are using in your page file and return a list of the locators that it could not find. If there are missing locators you can then rerun the generator to generate new selenium locators for your page. http://www.scottcsims.com