Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FindElement takes more than 10 minutes to return whether the element is present or not #229

Closed
yarafath8 opened this issue Apr 25, 2018 · 1 comment

Comments

@yarafath8
Copy link

yarafath8 commented Apr 25, 2018

Below is a sample code. If the element is present it works perfectly. But if the element is NOT present it takes almost 10 minutes to show 'NoSuchElementException ' and then comes to the Catch block.
The Default Search Time needs to be reduced in Winium.

       public void ServerConflict() throws Exception {

	try {
    	 WPF1.findElement(ConflictYesBtn).isDisplayed();
    	 WPF1.findElement(ConflictYesBtn).click();
    	 System.out.println("Button Present");
          } 
            catch (NoSuchElementException e) 
              {
    	 System.out.println("Button NOT Present");
           }
       }

I also used the fix from (https://github.com/2gis/Winium.Desktop/pull/71/commits) for ImplictWait.
But that does not work either.

Has anyone stumbled upon issue related to this. Please suggest

@yarafath8 yarafath8 changed the title FindElement takes more than 3 minutes to return whether the element is present or not FindElement takes more than 10 minutes to return whether the element is present or not Apr 25, 2018
@yarafath8
Copy link
Author

Managed to resolve this issue.

There was a performance issue at FindFirst() method. Will commit this fix soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant