testability-driver 1.0.4 → 1.1.0

data/config/sut_setup.rb

@@ -0,0 +1,32 @@
+############################################################################
+## 
+## Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies). 
+## All rights reserved. 
+## Contact: Nokia Corporation (testabilitydriver@nokia.com) 
+## 
+## This file is part of Testability Driver. 
+## 
+## If you have questions regarding the use of this file, please contact 
+## Nokia at testabilitydriver@nokia.com . 
+## 
+## This library is free software; you can redistribute it and/or 
+## modify it under the terms of the GNU Lesser General Public 
+## License version 2.1 as published by the Free Software Foundation 
+## and appearing in the file LICENSE.LGPL included in the packaging 
+## of this file. 
+## 
+############################################################################
+# Generic configuration file for sut setup.
+# Can be used to provide ruby code for sut configurations.
+module MobyBehaviour
+  module SUT
+	  # Setup method for sut that will be executed when @sut.setup is called  
+	  # Methods for sut can be called with self
+	  # Example:
+	  # self.run(:name => 'testapp')
+	  def setup
+		puts "Hello world"		
+	  end
+  end
+end
+  

data/config/sut_teardown.rb

@@ -0,0 +1,32 @@
+############################################################################
+## 
+## Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies). 
+## All rights reserved. 
+## Contact: Nokia Corporation (testabilitydriver@nokia.com) 
+## 
+## This file is part of Testability Driver. 
+## 
+## If you have questions regarding the use of this file, please contact 
+## Nokia at testabilitydriver@nokia.com . 
+## 
+## This library is free software; you can redistribute it and/or 
+## modify it under the terms of the GNU Lesser General Public 
+## License version 2.1 as published by the Free Software Foundation 
+## and appearing in the file LICENSE.LGPL included in the packaging 
+## of this file. 
+## 
+############################################################################
+# Generic configuration file for sut teardown.
+# Can be used to provide ruby code for sut configurations.
+module MobyBehaviour
+  module SUT
+	  # Teardown method for sut that will be executed when @sut.teardown is called  
+	  # Methods for sut can be called with self
+	  # Example:
+	  # self.application.close
+	  def teardown
+		puts "Bye world"		
+	  end
+  end
+end
+  

data/ext/extconf.rb

@@ -17,7 +17,7 @@
 ## 
 ############################################################################
 
-require File.join( File.dirname(__FILE__), '../lib/tdriver/util/loader' )
+require File.join( File.dirname(__FILE__), '../lib/tdriver/util/loader.rb' )
 
 MobyUtil::GemHelper.install( MobyUtil::FileHelper.tdriver_home ){ | tdriver_home_folder |
 
@@ -29,6 +29,8 @@ MobyUtil::GemHelper.install( MobyUtil::FileHelper.tdriver_home ){ | tdriver_home
     [ "../xml/parameters/tdriver_parameters.xml", "tdriver_parameters.xml", false ],
     [ "../xml/parameters/tdriver_parameters.xml", "default/tdriver_parameters.xml", true ],
     [ "../config/sut_parameters.rb", "sut_parameters.rb", true ],
+    [ "../config/sut_setup.rb", "sut_setup.rb", true ],
+    [ "../config/sut_teardown.rb", "sut_teardown.rb", true ],
 
     # templates
     [ "../xml/templates/*.xml",  "templates/", true ],

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::Application#closable?
+  As a test scripter writer
+  I want to use closable? method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Application behaviour
+
+  Scenario: Testing closable? 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].closable?()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::Application#close
+  As a test scripter writer
+  I want to use close method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Application behaviour
+
+  Scenario: Testing close 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].close()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing close method with optional argument 'options_hash' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].close(options_hash)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::Application#environment
+  As a test scripter writer
+  I want to use environment method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Application behaviour
+
+  Scenario: Testing environment 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].environment()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::Application#executable_name
+  As a test scripter writer
+  I want to use executable_name method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Application behaviour
+
+  Scenario: Testing executable_name 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].executable_name()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::Application#uid
+  As a test scripter writer
+  I want to use uid method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Application behaviour
+
+  Scenario: Testing uid 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].uid()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

data/lib/tdriver-devtools/tests/feature_tests/output/created.rid

@@ -0,0 +1 @@
+Thu, 16 Dec 2010 10:20:02 +0200

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

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::Find#find
+  As a test scripter writer
+  I want to use find method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::Find behaviour
+
+  Scenario: Testing find 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].find()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing find 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].find(attributes)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::FlashBehaviour#flash
+  As a test scripter writer
+  I want to use flash method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::FlashBehaviour behaviour
+
+  Scenario: Testing flash 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].flash()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::FlashBehaviour#flash_images
+  As a test scripter writer
+  I want to use flash_images method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::FlashBehaviour behaviour
+
+  Scenario: Testing flash_images 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].flash_images()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing flash_images method with optional argument 'flash_files' (Rename this to be more descriptive)
+    Given I launch application [APPLICATION_NAME] as @app
+    When I execute "@app.[SOME_OBJECT].flash_images(flash_files)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::SUT#application
+  As a test scripter writer
+  I want to use application method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing application 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].application()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing application 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].application(attributes)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#capture_screen
+  As a test scripter writer
+  I want to use capture_screen method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing capture_screen 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].capture_screen(arguments)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#child
+  As a test scripter writer
+  I want to use child method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing child 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].child(attributes)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#clear_verify_blocks
+  As a test scripter writer
+  I want to use clear_verify_blocks method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing clear_verify_blocks 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].clear_verify_blocks()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#connect
+  As a test scripter writer
+  I want to use connect method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing connect 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].connect(id)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SutController#execution_order
+  As a test scripter writer
+  I want to use execution_order method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SutController behaviour
+
+  Scenario: Testing execution_order 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].execution_order()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SutController#execution_order=
+  As a test scripter writer
+  I want to use execution_order= method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SutController behaviour
+
+  Scenario: Testing execution_order= 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].execution_order=(order)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

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

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#disconnect
+  As a test scripter writer
+  I want to use disconnect method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing disconnect 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].disconnect()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

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

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#freeze
+  As a test scripter writer
+  I want to use freeze method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing freeze 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].freeze()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

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

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#get_application_id
+  As a test scripter writer
+  I want to use get_application_id method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing get_application_id 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].get_application_id()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#get_object
+  As a test scripter writer
+  I want to use get_object method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing get_object 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].get_object(object_id)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#get_operator_data
+  As a test scripter writer
+  I want to use get_operator_data method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing get_operator_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].get_operator_data(operator_data_lname)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,15 @@
+Feature: MobyBehaviour::SUT#get_ui_dump
+  As a test scripter writer
+  I want to use get_ui_dump method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing get_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].get_ui_dump()"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+
+  Scenario: Testing get_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].get_ui_dump(refresh_args)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

@@ -0,0 +1,10 @@
+Feature: MobyBehaviour::SUT#get_user_information
+  As a test scripter writer
+  I want to use get_user_information method to [DO_SOMETHING] in [TARGET_APPLICATION]
+  so that I can test the MobyBehaviour::SUT behaviour
+
+  Scenario: Testing get_user_information 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].get_user_information(user_data_lname)"
+    Then [ADD_YOUR_VERIFICATION_HERE]
+

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

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