testability-driver 1.2.1 → 1.3.0

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

@@ -1,10 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

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

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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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]
-

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

@@ -1,15 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

@@ -1,20 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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

@@ -1,15 +0,0 @@
-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]
-