An implementation of the Page Object Pattern in Selenium along with a bunch of other features like KeyWords for oft used Webdriver calls, driver lifecycle management, effective logging and Test Script Templates
Other
2
stars
1
forks
source link
Document: Standardize the init() call in each of the ExtensibleServices and document the design strategy #10
init() method calls standardized
The design principle is that each of the service would have an init() method where the components of the service could be reassigned to specific implementations.
The init() method will have to be called after creating an object of the service by the enclosing service.
The super service of all services is the KeyWords which is injected into the JunitScript.
The KeyWord's init() need not be called explicitly but called during the create() method call, The kw object can be configured in the JunitScriptXYZ directly by fixing its components, this is to facilitate configuration either by using init calls or by dependency injection via Spring
The init() method does all the injections and calls on the init method of the enclosing object. This is propagated down the hierarchy.
init() method calls standardized The design principle is that each of the service would have an init() method where the components of the service could be reassigned to specific implementations. The init() method will have to be called after creating an object of the service by the enclosing service.
The super service of all services is the KeyWords which is injected into the JunitScript.
The KeyWord's init() need not be called explicitly but called during the create() method call, The kw object can be configured in the JunitScriptXYZ directly by fixing its components, this is to facilitate configuration either by using init calls or by dependency injection via Spring
The init() method does all the injections and calls on the init method of the enclosing object. This is propagated down the hierarchy.