Selenium WebDriver Plugin/en - Versionsgeschichte

Matilk: /* FAQ */ Firefox after Update

2024-08-22T15:16:05Z

FAQ: Firefox after Update

← Nächstältere Version		Version vom 22. August 2024, 15:16 Uhr
Zeile 272:		Zeile 272:
	:In most cases, the test can run in the back despite the overlay. However, the overlay counts as tap or window, meaning the block ''[Web] Get Window Handles'' for an example returns a window handle for it and you can switch to it. But you have options to get rid of it:		:In most cases, the test can run in the back despite the overlay. However, the overlay counts as tap or window, meaning the block ''[Web] Get Window Handles'' for an example returns a window handle for it and you can switch to it. But you have options to get rid of it:
	:* ''--disable-search-engine-choice-screen'': In the [[#Advanced_Settings\|advanced settings]] you can add the option <code>--disable-search-engine-choice-screen</code> and the overlay won't show up.		:* ''--disable-search-engine-choice-screen'': In the [[#Advanced_Settings\|advanced settings]] you can add the option <code>--disable-search-engine-choice-screen</code> and the overlay won't show up.
	:* ''Choose'': You can extend your test, so it actually chooses a search engine and closes the overlay. There are two things you need to bear in mind. First, you have to switch there using a ''Switch to Window'' block (e.g. by index ''2'' or with an empty title) and back to your original tab afterwards as well. Secondly, the interesting elements in the overlay are [[#~~Shadow_Elemens~~\|shadow elements]] and as such not directly displayed in the GUI-Browser.		:* ''Choose'': You can extend your test, so it actually chooses a search engine and closes the overlay. There are two things you need to bear in mind. First, you have to switch there using a ''Switch to Window'' block (e.g. by index ''2'' or with an empty title) and back to your original tab afterwards as well. Secondly, the interesting elements in the overlay are [[#Shadow_Elements\|shadow elements]] and as such not directly displayed in the GUI-Browser.

			*'''Firefox: <code>Process unexpectedly closed with status 0</code>'''
			:Error pattern: The connection to the Firefox browser fails with the error message <code>org.openqa.selenium.WebDriverException: Process unexpectedly closed with status 0</code>. However, the browser eventually opens without there being a connection in expecco.
			:A known cause of this issue is that the browser is started for the first time after an update, which the browser cannot handle properly in the automated state. The second attempt should then be successful. To prevent this error, make sure that you always start the browser normally the first time after an update.

Matilk: /* FAQ */ Chrome: Choose your search engine

2024-08-05T13:33:24Z

FAQ: Chrome: Choose your search engine

← Nächstältere Version		Version vom 5. August 2024, 13:33 Uhr
Zeile 266:		Zeile 266:
	*'''Additional Window Handles for Opera'''		*'''Additional Window Handles for Opera'''
	:The Opera browser returns more window handles as there are opened tabs or windows. They represent Opera internal features like ''Speed Dial'' or ''Better Address Bar Experience'' (BABE), which are embedded in the browser window, but not displayed like regular tabs. You can switch to these tabs using an appropriate action block, however not all actions are possible then, which can be used with the normal tabs. For example you cannot close them and they don't provide a screenshot. Therefore it is better to not even switch to their contexts. So be careful when switching to a tab by index, as the Opera tabs are among the others and the index might be a different one than for the other browser types.		:The Opera browser returns more window handles as there are opened tabs or windows. They represent Opera internal features like ''Speed Dial'' or ''Better Address Bar Experience'' (BABE), which are embedded in the browser window, but not displayed like regular tabs. You can switch to these tabs using an appropriate action block, however not all actions are possible then, which can be used with the normal tabs. For example you cannot close them and they don't provide a screenshot. Therefore it is better to not even switch to their contexts. So be careful when switching to a tab by index, as the Opera tabs are among the others and the index might be a different one than for the other browser types.

			*'''Chrome: Choose your search engine'''
			:Newer versions of Chrome show an [https://www.google.com/chrome/choicescreen/ overlay] at startup, where you have to choose a search engine. Usually, this choice is saved in the user profile. However, if you don't explicitly set a Chrome profile for the connection, each connect will use an empty profile and this question will always show up.

			:In most cases, the test can run in the back despite the overlay. However, the overlay counts as tap or window, meaning the block ''[Web] Get Window Handles'' for an example returns a window handle for it and you can switch to it. But you have options to get rid of it:
			:* ''--disable-search-engine-choice-screen'': In the [[#Advanced_Settings\|advanced settings]] you can add the option <code>--disable-search-engine-choice-screen</code> and the overlay won't show up.
			:* ''Choose'': You can extend your test, so it actually chooses a search engine and closes the overlay. There are two things you need to bear in mind. First, you have to switch there using a ''Switch to Window'' block (e.g. by index ''2'' or with an empty title) and back to your original tab afterwards as well. Secondly, the interesting elements in the overlay are [[#Shadow_Elemens\|shadow elements]] and as such not directly displayed in the GUI-Browser.

Matilk: /* Settings*/

2023-11-08T12:46:56Z

Settings

← Nächstältere Version		Version vom 8. November 2023, 12:46 Uhr
Zeile 10:		Zeile 10:

	(*) actually, there exists WebDriver interfaces to control Windows or OS X desktop applications. Thus, this plugin can be used in a number of additional scenarios.		(*) actually, there exists WebDriver interfaces to control Windows or OS X desktop applications. Thus, this plugin can be used in a number of additional scenarios.

			=Settings=
			This plugin uses the Java bridge and therefore needs a Java installation. You can specify it in the settings under ''Plugins'' -> ''Java Bridge''. The important field is ''Java Installation Path'', where you can set a JDK or JRE. If nothing is set, expecco tries to find java in the PATH.

			[[Datei:JDKPfadEinstellungen.png\|600px]]

			There are settings for the Selenium WebDriver Plugin itself as well. You find them under ''Plugins'' -> ''Webtest (Selenium WebDriver)''. There you can for example set the address of a remote running Selenium server or another Jar file for Selenium. The settings for the different browser types are divided into the two subpages ''Most Popular Browsers'' and ''Other Browsers''. There you can set the path to the browser executable or to the webdriver to use. You can leave all these fields empty and expecco will search for them automatically

	=Browser Support=		=Browser Support=

Matilk: /* Update WebDriver */

2023-09-25T15:12:23Z

Update WebDriver

← Nächstältere Version		Version vom 25. September 2023, 15:12 Uhr
Zeile 21:		Zeile 21:
	Usually, the driver is a separate program which translates WebDriver requests into browser-specific interface calls. However, there are also browsers and programs which have the WebDriver protocol already built in (eg. Safari).		Usually, the driver is a separate program which translates WebDriver requests into browser-specific interface calls. However, there are also browsers and programs which have the WebDriver protocol already built in (eg. Safari).

	The expecco installation package includes ~~drivers~~ for common browsers. However, you may have to ~~update~~ a driver~~, if the browser~~ version ~~changes~~. ~~The~~ ~~used~~ ~~drivers~~ ~~are~~ ~~located~~ in your expecco installation directory ~~below~~ the ~~installation~~ ~~folder~~ in:		The expecco installation package includes current driver versions for common browsers. However, as the browsers are updated continuously, sometimes even automatically, you sooner or later may have to download a new driver version. In that case put it in the folder inside your expecco installation directory where the other versions are stored as well, at:
	<code>packages/exept/expecco/plugin/seleniumWebDriver/lib</code>		<code>packages/exept/expecco/plugin/seleniumWebDriver/lib/XXX</code>
	(of course, with "\”s instead of "/"s on Microsoft Windows operating systems).		(of course, with "\”s instead of "/"s on Microsoft Windows operating systems), where "XXX" denotes the operating system (Windows, Linux, OSX etc.).
	To use a different driver, check the "Advanced" toggle in the connection dialog and add the driver's path to the settings (see below).		<!--To use a different driver, check the "Advanced" toggle in the connection dialog and add the driver's path to the settings (see below).-->

	In ~~some~~ ~~cases~~, expecco may show a warning, that the driver version ~~might be~~ incompatible with the browser. ~~This~~ ~~does~~ ~~not~~ ~~mean~~ ~~per~~ ~~se,~~ ~~that~~ ~~the~~ ~~combination~~ ~~does~~ ~~not work; instead~~, ~~it means~~ that ~~the~~ ~~combination~~ ~~has~~ not ~~been~~ ~~tested~~ by ~~eXept,~~ ~~but~~ ~~may nevertheless work~~. If ~~such~~ a ~~warning~~ ~~is shown, check~~ the ~~"''Do not show this~~ warning ~~again''" toggle~~, to ~~have~~ ~~expecco~~ ~~remember~~ that ~~combination as "trusted"~~ in ~~your~~ ~~settings~~.		In the connection dialog, expecco may show a warning, that the driver version is incompatible with the browser version. In some cases this may only be due to the fact, that this version was not known at the time of delivery. Some combinations may work despite the warning, but we cannot guarantee that for each individual case.

			Therefore you can always check the "''Do not show this warning again''" toggle, if such a warning is shown, to have expecco remember that combination as "compatible" in your settings, and not warn again. You should only do that, if you are sure that your tests will still be executed correctly. As we sometimes get compatibility problems ourselves and cannot always immediately find the reason, we advice you, to update the driver.

			For Chrome and Microsoft Edge, where each new browser version comes with a new driver version, you find a button in the connection dialog, to download matching driver versions by expecco.

	You find new driver versions at the following addresses:		You find new driver versions at the following addresses:

Matilk: Link to German version

2023-09-01T12:19:05Z

Link to German version

← Nächstältere Version		Version vom 1. September 2023, 12:19 Uhr
Zeile 1:		Zeile 1:
			[[Selenium_WebDriver_Plugin\|Deutsche Version]] \| '''English Version'''

	=Introduction=		=Introduction=
	Use the ''Selenium WebDriver Plugin'' to test or automate interactions of applications running in a web-browser (*). The plugin can be (and usually is) used with the [[Expecco_GUI_Tests_Extension_Reference\|GUI Browser]], which helps in the creation of tests. Moreover, the GUI Browser can record UI sessions, which can later be customised or refactored as required.		Use the ''Selenium WebDriver Plugin'' to test or automate interactions of applications running in a web-browser (*). The plugin can be (and usually is) used with the [[Expecco_GUI_Tests_Extension_Reference\|GUI Browser]], which helps in the creation of tests. Moreover, the GUI Browser can record UI sessions, which can later be customised or refactored as required.

Matilk: /* FAQ */ Opera Window Handles

2023-07-18T08:13:01Z

FAQ: Opera Window Handles

← Nächstältere Version		Version vom 18. Juli 2023, 08:13 Uhr
Zeile 250:		Zeile 250:
	*'''Key Chords with Shortcuts are not working'''		*'''Key Chords with Shortcuts are not working'''
	:Pressing keys simultaneously can be simulated using Key Chords. They can also be used to send shortcuts. However, not all inputs will work, as they are only sent to the page content, not to the browser itself. Combinations like ''Ctrl + t'' to open a new browser tab probably wont't work, ''Ctrl + a'' and ''Ctrl c'' on the other hand should be effective.		:Pressing keys simultaneously can be simulated using Key Chords. They can also be used to send shortcuts. However, not all inputs will work, as they are only sent to the page content, not to the browser itself. Combinations like ''Ctrl + t'' to open a new browser tab probably wont't work, ''Ctrl + a'' and ''Ctrl c'' on the other hand should be effective.

			*'''Additional Window Handles for Opera'''
			:The Opera browser returns more window handles as there are opened tabs or windows. They represent Opera internal features like ''Speed Dial'' or ''Better Address Bar Experience'' (BABE), which are embedded in the browser window, but not displayed like regular tabs. You can switch to these tabs using an appropriate action block, however not all actions are possible then, which can be used with the normal tabs. For example you cannot close them and they don't provide a screenshot. Therefore it is better to not even switch to their contexts. So be careful when switching to a tab by index, as the Opera tabs are among the others and the index might be a different one than for the other browser types.

Matilk: /* FAQ */ Stale Element Reference Exception

2023-06-12T14:47:38Z

FAQ: Stale Element Reference Exception

← Nächstältere Version		Version vom 12. Juni 2023, 14:47 Uhr
Zeile 234:		Zeile 234:
	*'''Error message <code>Cannot read property 'left' of undefined</code>'''		*'''Error message <code>Cannot read property 'left' of undefined</code>'''
	:The error <code>org.openqa.selenium.JavascriptException: javascript error: Cannot read property 'left' of undefined</code> can occur with the Chrome browser. This means that the used element is not visible. See the point above on that. The error is also known in combination with elements in a dropdown list, i.e. when clicking or moving the mouse over a <nowiki><option></nowiki> element within a <nowiki><select></nowiki> element. Such elements are generally not clickable. Instead, use a suitable <code>[Web] Select</code> block with the <nowiki><select></nowiki> element.		:The error <code>org.openqa.selenium.JavascriptException: javascript error: Cannot read property 'left' of undefined</code> can occur with the Chrome browser. This means that the used element is not visible. See the point above on that. The error is also known in combination with elements in a dropdown list, i.e. when clicking or moving the mouse over a <nowiki><option></nowiki> element within a <nowiki><select></nowiki> element. Such elements are generally not clickable. Instead, use a suitable <code>[Web] Select</code> block with the <nowiki><select></nowiki> element.

			*'''Error message: <code>Stale Element Reference Exception</code>'''
			:The error <code>org.openqa.selenium.StaleElementReferenceException</code> occurs whenever a WebElement is used that is no longer there. If that happens during your test and the element should have been there, try using the locator instead to fetch the element again. Maybe the error occurs because the test is currently in a different frame context as the element. If you are using [[#Compound_Paths\|compound paths]], the element should switch by itself to the correct context when it is used.
			:In rare cases this error can also occur in expecco itself, if at somewhere in the GUI browser or the recorder such a WebElement is used. You should then be able to abort and try again. Should the error persist, switch to the default content and refresh the tree in the GUI browser.

	*'''Block runs successfully, but without effect'''		*'''Block runs successfully, but without effect'''

Matilk: /* Shadow Elements */

2023-06-02T10:27:27Z

Shadow Elements

← Nächstältere Version		Version vom 2. Juni 2023, 10:27 Uhr
Zeile 190:		Zeile 190:

	If you want to record the combined paths or use them in the GUI Browser, check the box ''Record Compound Paths'' in the ''GUI Browser'' menu under ''Recording''. This will create and display a compound path for embedded elements relative to the current context, instead of only within its own context as before. You can also address these elements directly in the recorder or find them via Follow-Mouse.		If you want to record the combined paths or use them in the GUI Browser, check the box ''Record Compound Paths'' in the ''GUI Browser'' menu under ''Recording''. This will create and display a compound path for embedded elements relative to the current context, instead of only within its own context as before. You can also address these elements directly in the recorder or find them via Follow-Mouse.

			=Shadow Elements=
			Shadow DOMs allow you to encapsulate parts of a page from the remaining document. They provide a way to attach hidden shadow elements to an element. You can find a more detailed explanation for example here: [https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_shadow_DOM Using shadow DOM - Web APIs \| MDN].

			The SeleniumWebDirverLibrary has the block ''[Web] Get Shadow DOM'', which gives you the topmost elements, which then can be used like other WebElements.

			As the elements are hidden, they are not directly displayed in the GUI browser. However, since expecco 23.1 you can check in the context menu of the elements in the GUI browser the option to find shadow elements. They then will be displayed when updating the children of an element, if there are any, but not when updating the whole tree. If the option is checked, the elements are also available in the recorder.

			==Compound Paths==
			Similar to elements inside a frame, shadow elements can be accessed by compound paths. These paths can be used directly at the library blocks and the block ''[Web] Get Shadow DOM'' is not required. The paths are of the form
			<host path>/shadowRoot/<shadow path>
			where ''<host path>'' denotes the path to the element that has the shadow DOM attached, and ''<shadow path>'' denotes the path inside the shadow DOM to the desired element. '/shadowRoot' serves as marker where the switch to the shadow DOM is needed.

	=Authentication Alerts=		=Authentication Alerts=

Matilk: Embedded Content and expecco 23.1 improvements

2023-03-13T17:18:41Z

Embedded Content and expecco 23.1 improvements

@@ Zeile 181: / Zeile 181: @@
 #'''Set Screen Scale to Fit Window''': Scale the screenshot to fully fit in the window
 #'''Scale''': Changes the scale of the screenshot. Can also be adjusted by scrolling with pressed <kbd>CTRL</kbd> key.
 =Authentication Alerts=

Matilk: /* Update WebDriver */ new ChromeDriver download site

2022-11-07T14:11:24Z

Update WebDriver: new ChromeDriver download site

← Nächstältere Version		Version vom 7. November 2022, 14:11 Uhr
Zeile 29:		Zeile 29:
	{\|		{\|
	\|Chrome/Chromium		\|Chrome/Chromium
	\|[https://sites.google.com/a/chromium.org/~~chromedriver~~/~~downloads~~ ChromeDriver]		\|[https://sites.google.com/chromium.org/driver/ ChromeDriver]
	\|-		\|-
	\|Edge		\|Edge