org.jboss.arquillian.ajocado.framework.internal

Class SeleniumExtensionsImpl

java.lang.Object

org.jboss.arquillian.ajocado.framework.internal.SeleniumExtensionsImpl

All Implemented Interfaces:

SeleniumExtensions

public class SeleniumExtensionsImpl
extends Object
implements SeleniumExtensions

Defines the methods for loading the Selenium JS extensions to the Selenium Test Runner window.

Version:

$Revision$

Author:

Lukas Fryc

Constructor Summary

Constructors

Constructor and Description
SeleniumExtensionsImpl()

Method Summary

Methods

Modifier and Type	Method and Description
void	registerCustomHandlers() The SeleniumExtensions specifies new custom handlers, but the registration in commandFactory are triggered before the loading of extensions.
void	requireResource(String resourceName) Loads the JavaScript extension by it's resourceName.
void	requireResources(List<String> resourceNames) Adds the JavaScript extensions by defining list of resource names.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

SeleniumExtensionsImpl

public SeleniumExtensionsImpl()

Method Detail

requireResource

public void requireResource(String resourceName)

Loads the JavaScript extension by it's resourceName.

If the JavaScript with given resourceName are already loaded, it will not be loaded again.

If the JavaScript is already loaded but it's source has another checksum, it will be reloaded.

Specified by:

requireResource in interface SeleniumExtensions

Parameters:

resourceName - the full path to resource

requireResources

public void requireResources(List<String> resourceNames)

Adds the JavaScript extensions by defining list of resource names.

Specified by:

requireResources in interface SeleniumExtensions

Parameters:

resourceNames - the list of full paths to resources

registerCustomHandlers

public void registerCustomHandlers()

The SeleniumExtensions specifies new custom handlers, but the registration in commandFactory are triggered before the loading of extensions. That is reason why we must explicitly register it before the test after each start of selenium.

Specified by:

registerCustomHandlers in interface SeleniumExtensions