-
Notifications
You must be signed in to change notification settings - Fork 24
Failure Details says "null" when it cannot find an Element on self-hosted Selenium Server #43
Comments
In this case, the "Execution Status" is always "Running" , and it never goes into "Error" mode. I will have to manually delete the "TestSuiteID" in order to re-execute the test. |
I don't have a setup to test this, but this seems odd because the code that populates the error into a TestExectution is the same no matter what provider is used. Can you confirm that your self-hosted selenium server is giving the same response as saucelabs when a WebElement isn't found? This is what I see when a webelement isn't found on saucelabs: |
It looks like my selenium server throws an exception in this case. I see the below stacktrace on my selenium server in this case. *** Element info: {Using=css selector, value=#Account_Tab > a}
rce) |
If a test fails as it cannot find an WebElement, the failure that it returns is null on a self-hosted Selenium Server.
How can I make get the correct Failure and store it ? Appreciate your help. Thanks.
The text was updated successfully, but these errors were encountered: