testability-driver 1.0.4 → 1.1.0

data/lib/tdriver-devtools/tests/feature_tests/output/sut_parameter.feature

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::SUT#parameter
+  As a test scripter writer
+  I want to use parameter method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing parameter method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].parameter()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing parameter method with optional argument 'arguments' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].parameter(arguments)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_press_key.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#press_key
+  As a test scripter writer
+  I want to use press_key method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing press_key method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].press_key(value)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_received_data.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#received_data
+  As a test scripter writer
+  I want to use received_data method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing received_data method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].received_data()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_refresh.feature

@@ -0,0 +1,20 @@
+Feature: MobyBehaviour::SUT#refresh
+  As a test scripter writer
+  I want to use refresh method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing refresh method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing refresh method with optional argument 'refresh_args' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh(refresh_args)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing refresh method with optional argument 'creation_attributes' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh(refresh_args, creation_attributes)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_refresh_timeout.feature

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::SUT#refresh_timeout=
+  As a test scripter writer
+  I want to use refresh_timeout attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing refresh_timeout attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_timeout"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing refresh_timeout= attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_timeout="
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_refresh_tries.feature

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::SUT#refresh_tries=
+  As a test scripter writer
+  I want to use refresh_tries attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing refresh_tries attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_tries"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing refresh_tries= attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_tries="
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_refresh_ui_dump.feature

@@ -0,0 +1,20 @@
+Feature: MobyBehaviour::SUT#refresh_ui_dump
+  As a test scripter writer
+  I want to use refresh_ui_dump method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing refresh_ui_dump method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_ui_dump()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing refresh_ui_dump method with optional argument 'refresh_args' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_ui_dump(refresh_args)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing refresh_ui_dump method with optional argument 'creation_attributes' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].refresh_ui_dump(refresh_args, creation_attributes)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_run.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#run
+  As a test scripter writer
+  I want to use run method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing run method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].run(target)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_sent_data.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#sent_data
+  As a test scripter writer
+  I want to use sent_data method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing sent_data method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].sent_data()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_state.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#state
+  As a test scripter writer
+  I want to use state method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing state method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].state()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_translate.feature

@@ -0,0 +1,30 @@
+Feature: MobyBehaviour::SUT#translate
+  As a test scripter writer
+  I want to use translate method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing translate method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].translate(logical_name)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing translate method with optional argument 'file_name' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].translate(logical_name, file_name)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing translate method with optional argument 'plurality' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].translate(logical_name, file_name, plurality)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing translate method with optional argument 'numerus' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].translate(logical_name, file_name, plurality, numerus)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing translate method with optional argument 'lengthvariant' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].translate(logical_name, file_name, plurality, numerus, lengthvariant)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_ui_type.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#ui_type
+  As a test scripter writer
+  I want to use ui_type attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing ui_type attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].ui_type"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_ui_version.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#ui_version
+  As a test scripter writer
+  I want to use ui_version attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing ui_version attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].ui_version"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_unfreeze.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#unfreeze
+  As a test scripter writer
+  I want to use unfreeze method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing unfreeze method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].unfreeze()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_update.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#update
+  As a test scripter writer
+  I want to use update method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing update method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].update()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_verify_always.feature

@@ -0,0 +1,20 @@
+Feature: MobyBehaviour::SUT#verify_always
+  As a test scripter writer
+  I want to use verify_always method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing verify_always method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].verify_always(expected)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing verify_always method with optional argument 'message' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].verify_always(expected, message)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing verify_always method with optional argument 'block' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].verify_always(expected, message, block)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_verify_blocks.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#verify_blocks
+  As a test scripter writer
+  I want to use verify_blocks attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing verify_blocks attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].verify_blocks"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_x_path.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#x_path
+  As a test scripter writer
+  I want to use x_path attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing x_path attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].x_path"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_xml_data.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#xml_data
+  As a test scripter writer
+  I want to use xml_data attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing xml_data attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].xml_data"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_xml_data_0x3d.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#xml_data=
+  As a test scripter writer
+  I want to use xml_data= method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing xml_data= method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].xml_data=(xml)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/sut_xml_data_crc.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#xml_data_crc
+  As a test scripter writer
+  I want to use xml_data_crc attribute to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing xml_data_crc attribute (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].xml_data_crc"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/switchbox_behaviour_power_down.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SwitchboxBehaviour#power_down
+  As a test scripter writer
+  I want to use power_down method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SwitchboxBehaviour behaviour
+
+  Scenario: Testing power_down method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].power_down()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/switchbox_behaviour_power_status.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SwitchboxBehaviour#power_status
+  As a test scripter writer
+  I want to use power_status method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SwitchboxBehaviour behaviour
+
+  Scenario: Testing power_status method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].power_status()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/switchbox_behaviour_power_up.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SwitchboxBehaviour#power_up
+  As a test scripter writer
+  I want to use power_up method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SwitchboxBehaviour behaviour
+
+  Scenario: Testing power_up method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].power_up()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/switchbox_behaviour_reset.feature

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SwitchboxBehaviour#reset
+  As a test scripter writer
+  I want to use reset method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SwitchboxBehaviour behaviour
+
+  Scenario: Testing reset method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].reset()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/verification_test_object_exists_0x3f.feature

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::Verification#test_object_exists?
+  As a test scripter writer
+  I want to use test_object_exists? method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Verification behaviour
+
+  Scenario: Testing test_object_exists? method with required argument(s) (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].test_object_exists?(type)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing test_object_exists? method with optional argument 'attributes' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].test_object_exists?(type, attributes)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver/base/behaviour/behaviours/object_composition.rb

@@ -61,7 +61,7 @@ module MobyBehaviour
 		# === raises
 		def add_parent( parent_object )
 
-      warn("Warning: Deprecated method, use store to @parent instead of using this method") 
+      warn("warning: Deprecated method, use store to @parent instead of using this method") 
 
 			@parent = parent_object
 
@@ -75,7 +75,7 @@ module MobyBehaviour
 		# ?
 		def remove_parent()
 
-      warn("Warning: Deprecated method, set @parent to nil instead of using this method") 
+      warn("warning: Deprecated method, set @parent to nil instead of using this method") 
 
 			@parent = nil
 
@@ -90,7 +90,7 @@ module MobyBehaviour
 		# === raises
 		def add_child( new_child_object ) 
 
-      warn("Warning: Deprecated method, use @child_object_cache.add_object instead of this method")
+      warn("warning: Deprecated method, use @child_object_cache.add_object instead of this method")
 
 			@_child_object_cache.merge!( new_child_object.hash => new_child_object )
 
@@ -105,7 +105,7 @@ module MobyBehaviour
 		# === raises
 		def remove_child( target_child_object )
 
-      warn("Warning: Deprecated method, use @child_object_cache.add_object instead of this method")
+      warn("warning: Deprecated method, use @child_object_cache.add_object instead of this method")
 
 			@_child_object_cache.delete( target_child_object.hash )
 

data/lib/tdriver/base/behaviour/factory.rb

@@ -112,6 +112,14 @@ module MobyBase
     end
 
   end
+  
+  # TODO: document me
+  def reset_modules_cache
+  
+    # reset modules cache hash; needed if new behaviour plugins loaded later than when initializing TDriver/SUT
+    @@modules_cache.clear
+  
+  end
 
   def apply_behaviour!( rules = {} )
 

data/lib/tdriver/base/sut/generic/behaviours/application.rb

@@ -162,15 +162,19 @@ module MobyBehaviour
         end
 
         # Disable logging
-        $logger.enabled = false if ( original_logger_state = $logger.enabled )
+        original_logger_state = $logger.enabled
+        $logger.enabled = false
 
         # verify close results
+        # store start time
+          start_time = Time.now
+          timeout_time = $parameters[ self.sut.id ][ :application_synchronization_timeout, '60' ].to_f
         begin
 
           application_identification_hash = { :type => 'application', :id => @id }
 
           MobyUtil::Retryable.until(
-            :timeout => $parameters[ self.sut.id ][ :application_synchronization_timeout, '60' ].to_f,
+            :timeout => timeout_time,
             :interval => $parameters[ self.sut.id ][ :application_synchronization_retry_interval, '0.25' ].to_f,
             :exception => MobyBase::VerificationError,
             :unless => [MobyBase::TestObjectNotFoundError, MobyBase::ApplicationNotAvailableError] ) {
@@ -185,7 +189,7 @@ module MobyBehaviour
             if ( close_options[ :check_process ] == true ) 
 
               # the application did not close
-              raise MobyBase::VerificationError.new, "Verification of close failed. The application that was to be closed is still running." if matches.count > 0
+              raise MobyBase::VerificationError.new, "Verification of close failed. The application that was to be closed is still running." if matches.count > 0 && (Time.now - start_time) >= timeout_time
 
             elsif ( close_options[ :check_process ] == false )
 
@@ -359,6 +363,23 @@ module MobyBehaviour
 
 	end
 
+	# == description
+	# Returns the mem usage of the application if the information is available.
+	# Will return -1 if the information is not available.
+	# 
+	# == returns
+	# Integer
+	#   description: Current memory usage
+	#   example: 124354
+	#
+	def mem_usage
+	  mem = -1
+	  begin
+		mem = self.attribute('memUsage')
+	  rescue
+	  end
+	  mem
+	end
 
 
     # enable hooking for performance measurement & debug logging