Recent changes to Handlers

Handlers modified by Bartek Wilczek

Bartek Wilczek — Tue, 01 Jul 2014 09:26:55 -0000

--- v4
+++ v5
@@ -11,7 +11,7 @@
     browser = webdriver_handler.driver

     # In other handlers:
-    webdriver_handler = @test.handler( :webdriver )
+    webdriver_handler = @runner.get_handler( :webdriver )
     browser = webdriver_handler.driver

 The code above will set webdriver_handler variable to reference to instance of Webdriver hander object that is created once per whole test execution process. If there's a need to have multiple instances of the same handler class (for example to have multiple browser sessions for one test) additional parameter instance_id has to be introduced to 'handler' function call:

WikiPage Handlers modified by Bartek Wilczek

Bartek Wilczek — Wed, 07 Mar 2012 14:53:37 -0000

--- v3 
+++ v4 
@@ -26,4 +26,4 @@
 
 ### Life cycle
 
-asd
+An instance of handler class is created when handler() function is called for the first time in any place of the code. Handler class implements Listener interface, so it supports methods start_exec, start_test, start_variant, end_variant, end_test, end_exec. When first instantiated execution control flow is inside 'variant' so the following 3 methods are executed: start_exec, start_test, start_variant. Initialization of objects needed throughout the whole execution should be set in start_exec and cleaned up in end_exec. Other start/end methods can be used to manipulate these internal objects: for example Webdriver handler uses start_variant method to restart browser window on each variant.

WikiPage Handlers modified by Bartek Wilczek

Bartek Wilczek — Wed, 07 Mar 2012 14:35:46 -0000

--- v2 
+++ v3 
@@ -6,7 +6,23 @@
 
 ### Accessing handlers from test code
 
-asd
+    # In test code:
+    webdriver_handler = handler( :webdriver )
+    browser = webdriver_handler.driver
+
+    # In other handlers:
+    webdriver_handler = @test.handler( :webdriver )
+    browser = webdriver_handler.driver
+    
+The code above will set webdriver_handler variable to reference to instance of Webdriver hander object that is created once per whole test execution process. If there's a need to have multiple instances of the same handler class (for example to have multiple browser sessions for one test) additional parameter instance_id has to be introduced to 'handler' function call:
+
+    # In test code:
+    webdriver_handler = handler( :webdriver, 2 )
+    browser = webdriver_handler.driver
+
+    # In other handlers:
+    webdriver_handler = @test.handler( :webdriver, 2 )
+    browser = webdriver_handler.driver
 
 ### Life cycle

WikiPage Handlers modified by Bartek Wilczek

Bartek Wilczek — Wed, 07 Mar 2012 13:56:17 -0000

--- v1 
+++ v2 
@@ -1,1 +1,13 @@
+### Introduction
+
 Each test in bubik is represented by an independent object (instance of Scenario class). It's lifetime is limited only to time of 'run' method execution. None of the object created inside a test can be reused in other tests. Therefore the concept of handlers has been introduced.
+
+Handler is an instance of a class that extends Bubik::Handler and is located in module Bubik::Handlers. Built-in handlers like 'webdriver' are located in BUBIK_DIR/handlers. Project specific handler should be located in PROJECT_DIR/handlers. Both directories are scanned for proper classes when handler object is requested from the test code for the first time.
+
+### Accessing handlers from test code
+
+asd
+
+### Life cycle
+
+asd

WikiPage Handlers modified by Bartek Wilczek

Bartek Wilczek — Wed, 07 Mar 2012 13:17:34 -0000

Each test in bubik is represented by an independent object (instance of Scenario class). It's lifetime is limited only to time of 'run' method execution. None of the object created inside a test can be reused in other tests. Therefore the concept of handlers has been introduced.