test-factory 0.5.1 → 0.5.2

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    NTUzYjI3ZWNiZjVjZWI5M2NkODU2MDIzYjg1YmQ5MDczMjliMzAxNw==
+    NjM5YzM1ZTU5OTNjNGI1OTQ2ODkxODg0ZTJlNDk2ZjIxMzZhMzRmNw==
   data.tar.gz: !binary |-
-    NDRiNjc2ZWNiNzUxY2Y1NmZiNzA0YjUxYWY5NWNjOGVjYjFmOGMzMw==
+    NjYwMmM4Y2IyMmE0NTgzNDBlYzMzYjZhMTM5OGM1OTE0MGYxMmIzYQ==
 !binary "U0hBNTEy":
   metadata.gz: !binary |-
-    NWE2ZjM5OTdkYTk4ZTllMGY0ZDkxMGM1ZWFjZDE5MGQyY2QxYTFlNTE0Njk2
-    ZjY3ODM5NzVkZmE4ZDIyZjgxNTJmODEwMDFjZTc2MmJkYTUwMDMwMWVmNzFm
-    NDRjNGY4Y2RjYTE4ZDE3ZDMzMzExYzgzYzllMTQ4NGVjYmE2ZDU=
+    NDUxMTI3NTZmYTA2MWIxM2VkOGExOWU1MTNkOWI2NzVkMTNjYjNkZTNhMmNm
+    NTM5MGQ4YjBlNWY3MWVjMzM2YmUwM2FkYTViYzQzY2ZlYjVkZjY5NTQwZWRj
+    NmE4ZDc2YTA5NGIzNmFhMWE1YjA4ZWI0Yjk4ZDA0ZGNkNzBhYmM=
   data.tar.gz: !binary |-
-    YTQ5MTg4MDZhNDI5ZTY2ZGVjMDVhYjc5MmNlOGExM2QxOGRkMmMzZmY0MzY1
-    NDE3MTliNjBkMDg3NjU0NjE5NDRiOGUxMDM5NmJhYTczMTFhYjZlZmMxZWFk
-    N2I1ZTRiMjQ2MDEwOTk3ZDM2ODI4ODM2MDEwOTM3NTliZDE5OGI=
+    OTc0ZmIzNzk2NDA3NjcwZWZiMWViNDg4ZDdjMTEyZTY2OTRkNDRiMTZmZDMw
+    NWI4OGM1Yzg5YzliNTQ4OTk5MmQxNjkyMDJjMWRlZDk3NDJjMDgxM2Q0MDUw
+    MjYzNTQwM2VkZTUyODkyNWQ5N2QzNjMyZTUzZWNiNWJmYWE3MmQ=

data/lib/test-factory/data_factory.rb

@@ -16,6 +16,7 @@
 class DataFactory
 
   include Foundry
+  extend Forwardable
 
   # Since Data Objects are not "Marshallable", and they generally
   # contain lots of types of data in their instance variables,

data/lib/test-factory/page_factory.rb

@@ -147,6 +147,31 @@ class PageFactory
       elementize(:button, button_text, *alias_name)
     end
 
+    # TestFactory doesn't allow defining a method in a child class
+    # with the same name as one already defined in a parent class.
+    # The thinking here is: "Out of sight, out of mind." Meaning:
+    # you or a team mate might not know or have forgotten that a given
+    # element is already defined in a parent class, and so define it
+    # again. TestFactory's restriction is there to help prevent this.
+    #
+    # However, in some cases you may have a child page class with a
+    # special circumstance, where the parent class's version of the
+    # method really doesn't apply, and you want to use the same method
+    # name in this child class because, really, no other method name
+    # would fit quite as well.
+    #
+    # The #undefine method is for those rare cases. Note: If you start
+    # using this method a lot then you should consider that a sign
+    # that perhaps you're putting too many method definitions into
+    # parent page classes.
+    #
+    # @example
+    #   undefine :status, :doc_id => Undefines the specified methods in the current class
+    #
+    def undefine *methods
+      methods.each{ |m| undef_method m }
+    end
+
     def inherited klass
       klass.instance_eval {
 

data/lib/test-factory.rb

@@ -13,5 +13,6 @@
 # limitations under the License.
 
 require 'watir-webdriver'
+require 'forwardable'
 %w{foundry.rb data_factory.rb}.each { |f| require "#{File.dirname(__FILE__)}/test-factory/#{f}" }
 Dir["#{File.dirname(__FILE__)}/test-factory/*.rb"].each {|f| require f }

data/test-factory.gemspec

@@ -1,6 +1,6 @@
 spec = Gem::Specification.new do |s|
   s.name = 'test-factory'
-  s.version = '0.5.1'
+  s.version = '0.5.2'
   s.summary = %q{rSmart's framework for creating automated testing scripts}
   s.description = %q{This gem provides a set of modules and methods to help quickly and DRYly create a test automation framework using Ruby and Watir (or watir-webdriver).}
   s.files = Dir.glob("**/**/**")

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: test-factory
 version: !ruby/object:Gem::Version
-  version: 0.5.1
+  version: 0.5.2
 platform: ruby
 authors:
 - Abraham Heward
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-07-23 00:00:00.000000000 Z
+date: 2014-08-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: watir-webdriver