ArtOfTest.WebAii.Core
Generic action support for all browser types.
The different annotation modes
Class represents a browser instance managed by the Manager. This object exposes all the browser specific information and methods to automate the underlying browser that this instance represents.
The different common categories of browser caching.
Thrown when invalid configuration operation is performed.
Show configuration status for the specified browser.
The browser execution type. (i.e. firefox, internet explorer ...etc). The real browser type users can choose from.
The browser type. (i.e. firefox, internet explorer ...etc).
Class representing the desktop input devices. Mouse and Keyboard.
Class representing desktop settings configuration section handler
Holds a single clause as part of a Silverlight element FindExpression.
Holds a Silverlight element FindExpression.
Dummy search type.
Provides infrastructure for accessing elements defined by FindParamAttribute on test methods and classes. Replaces the Find.Elements dictionary which has been obsoleted.
The different type of element-dom synchronization supported by the framework and the SyncManager.
Enum extension methods.
Class provides quick search routines for finding an element(s) within a document.
Defines which reference type the Find object is using.
Information regarding a specific frame
Collection of frames (Browser objects)
An Html specific find clause.
An Html find expression. This expression replaced FindParams that are being deprecated.
Different types of supported find expressions.
Type of local web servers available for tests.
Log support for the framework and test cases.
The types of logging available in WebAii.
This class manages the life spans and instances of all browser objects in the framework. It also manages the communication pipeline between the framework and all browsers.
Event handler for ActiveBrowserChanged event.
A general purpose collection
The different types of mouse events to perform.
The mouse wheel turn directions.
The different annotation modes
The different annotation modes
Handler for "WebAii.Settings.ResponsiveWeb" section
Type of script events that can be invoked on an html element.
Used to configure what the default scroll to visible behavior is.
Class representing the settings to be used when initializing the framework.
Settings for responsive web.
Settings object config section handler. Use this object to read a Settings config section in a .config file.
You can persist the settings for your application/test cases in a config file.The following is a sample config file that holds certain settings. Any settings not specified in this section, their values will be set to the system defaults:
<?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <section name="WebAii.Settings" type="ArtOfTest.WebAii.Core.SettingsConfigSectionHandler,ArtOfTest.WebAii"/> </configSections>
<WebAii.Settings defaultBrowser="InternetExplorer" logLocation="D:\Log" executionTimeout="30000" clientReadyTimeout="60000" localWebServer="None"; webAppPhysicalPath="c:\Inetpub\wwwroot\MyApplication" enableScriptLogging="false" queryEventLogErrorsOnExit="false" enableUILessRequestViewing="false" baseUrl="http://www.testsite.com/" executionDelay="0" annotateExecution="false" annotationMode="All" logAnnotations="false" simulatedMouseMoveSpeed="0.3f" waitCheckInterval="500" aspNetDevServerPort="-1" createLogFile="true" killBrowserProcessOnClose="false" killBrowsersBeforeStart="false" recycleBrowser="false" useHttpProxy="false" enableSilverlight="false" xMultiMgr="false" silverlightConnectTimeout="60000" elementWaitTimeout="15000" />
</configuration>
In your code, you can get these settings by using the SettingsConfigSectionHandler like this:
SettingsConfigSectionHandler settingsSection = (SettingsConfigSectionHandler)ConfigurationManager.GetSection("WebAii.Settings"); Settings mySettings = new Settings(settingsSection);
You can then use mySettings to pass in to the Manager constructor.
The Telerik Components version to use
Specifies the action that the DialogMonitor should take when it encounters unexpected dialogs
Configuration section for WPF settings.