You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
I have a self-hosted Selenium Server, and when I run my tests the "Execution Status" is always in "Running" mode, and it never goes into "Error" mode when there are any errors such as "cannot find a webelement".
Due to this my entire test suite is not executed. I will have to manually delete the "TestSuiteID" in order to re-execute the test. Is there a way to fix this ? Appreciate your help. Thanks.
This could be caused by Issue # 43 (#43), but just want to track this as a separate issue.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a self-hosted Selenium Server, and when I run my tests the "Execution Status" is always in "Running" mode, and it never goes into "Error" mode when there are any errors such as "cannot find a webelement".
Due to this my entire test suite is not executed. I will have to manually delete the "TestSuiteID" in order to re-execute the test. Is there a way to fix this ? Appreciate your help. Thanks.
This could be caused by Issue # 43 (#43), but just want to track this as a separate issue.
The text was updated successfully, but these errors were encountered: