How to set TESTAR with Webdriver protocol: Difference between revisions
Update Webdriver protocol web page |
Insert webdriver protocol images |
||
| Line 1: | Line 1: | ||
== Usage of TESTAR WebDriver == | ==Usage of TESTAR WebDriver== | ||
The webdriver version of TESTAR is developed to better handle web applications. For various reasons, the desktop version doesn't recognize the non-native widgets available in websites. TESTAR webdriver tries to remedy this by looking at the DOM and adding a (JS) web extension to the browser. An additional advantage is the fact that it is safe to run the webdriver version 'natively', i.e. it is not necessary to run TESTAR webdriver in a VM. | The webdriver version of TESTAR is developed to better handle web applications. For various reasons, the desktop version doesn't recognize the non-native widgets available in websites. TESTAR webdriver tries to remedy this by looking at the DOM and adding a (JS) web extension to the browser. An additional advantage is the fact that it is safe to run the webdriver version 'natively', i.e. it is not necessary to run TESTAR webdriver in a VM. | ||
The webdriver version of TESTAR is tested on 3 mayor platforms : Windows 10, OS X and Linux. It has been tested with Chrome/Chromium, Firefox and Edge (Windows). That said, using Chrome seems to be the most performant option. | The webdriver version of TESTAR is tested on 3 mayor platforms : Windows 10, OS X and Linux. It has been tested with Chrome/Chromium, Firefox and Edge (Windows). That said, using Chrome seems to be the most performant option. | ||
== Advanced configuration for webdriver protocol == | ==Advanced configuration for webdriver protocol== | ||
=== SUT web domain === | ===SUT web domain=== | ||
[[File:Webdriver domains allowed.png|none|thumb]] | <br />[[File:Webdriver domains allowed.png|none|thumb]] | ||
[[File:Webdriver follow link.png|none|thumb]] | |||
<br /> | <br /> | ||
=== SUT clickable elements === | ===SUT clickable elements=== | ||
While the webdriver tries to find all clickable elements on the page via the onclick attribute or eventlistener, this is not sufficient for certain web frameworks that use global eventlisteners. Global eventListeners use class attributes to determine the required actions when the element is clicked. The protocol allows the tester to add these attributes to clickableClasses. | While the webdriver tries to find all clickable elements on the page via the onclick attribute or eventlistener, this is not sufficient for certain web frameworks that use global eventlisteners. Global eventListeners use class attributes to determine the required actions when the element is clicked. The protocol allows the tester to add these attributes to clickableClasses. | ||
<br /> | <br /> | ||
[[File:Webdriver clickable classes.png|none|thumb]] | |||
=== Web denied extensions === | |||
===Web denied extensions=== | |||
[[File:Webdriver denied extensions.png|none|thumb]] | |||
<br /> | |||
<br /> | <br /> | ||
=== Web login === | ===Web login=== | ||
<br /> | |||
[[File:Webdriver login form.png|none|thumb]] | |||
<br /> | <br /> | ||
=== Web policy popups === | ===Web policy popups=== | ||
<br /> | |||
[[File:Webdriver policy popups.png|none|thumb]] | |||
<br /> | <br /> | ||
Revision as of 18:52, 15 September 2019
Usage of TESTAR WebDriver
The webdriver version of TESTAR is developed to better handle web applications. For various reasons, the desktop version doesn't recognize the non-native widgets available in websites. TESTAR webdriver tries to remedy this by looking at the DOM and adding a (JS) web extension to the browser. An additional advantage is the fact that it is safe to run the webdriver version 'natively', i.e. it is not necessary to run TESTAR webdriver in a VM.
The webdriver version of TESTAR is tested on 3 mayor platforms : Windows 10, OS X and Linux. It has been tested with Chrome/Chromium, Firefox and Edge (Windows). That said, using Chrome seems to be the most performant option.
Advanced configuration for webdriver protocol
SUT web domain
SUT clickable elements
While the webdriver tries to find all clickable elements on the page via the onclick attribute or eventlistener, this is not sufficient for certain web frameworks that use global eventlisteners. Global eventListeners use class attributes to determine the required actions when the element is clicked. The protocol allows the tester to add these attributes to clickableClasses.
Web denied extensions
Web login
Web policy popups
