Display results as :

Rechercher Advanced Search

Latest topics
» Geting issues in identifying the elsements in webdriver
Fri Feb 17, 2017 4:41 pm by janbaskt

» WebDriver - why not to use a singlton for it?
Fri Feb 17, 2017 4:40 pm by janbaskt

» WebDriver session when using testng annotation to invoke driver instance
Fri Feb 17, 2017 4:39 pm by janbaskt

» Selenium fails to launch Chrome
Fri Feb 17, 2017 4:39 pm by janbaskt

» why do i get this error
Fri Feb 17, 2017 4:38 pm by janbaskt

» Selenium Tutorial
Thu Feb 16, 2017 5:21 pm by Rahul

» When to use Selenium IDE, RC and WebDriver
Mon Feb 13, 2017 2:35 pm by azharuddin

» How to integrate selenium with ZAPI-Zephyr
Sat Feb 11, 2017 2:25 am by gseera002c

» Selenium Webdriver
Sat Feb 04, 2017 6:47 pm by


FindElement Exception Behavior

View previous topic View next topic Go down

FindElement Exception Behavior

Post by iwan933 on Mon Jul 08, 2013 1:53 pm


is there a possibility to change the Exception behavior on FindElement method in next Version?
The behavior like WaTiN got it would be most Userfriendly, if element is not found, store Exception, and set Exists Attribute to false.
If the element object is forced to invoke a method, while it does not Exist, throw the stored Exception.

This would save me many try-catch-blocks, as i often need to check if elements Exists and then use them. Using the HasElement Extension
does not really solve my problem, as i have to re-search the element to use it, which feels weird.



Posts : 1
Join date : 2013-07-08

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum