scriby / browser-harness Goto Github PK

Add the ability to pass an error message to waitFor

It's 100ms now, around 20ms looks good.

The approach looks really interesting, compared to using Selenium.

Is the project still maintained, or have some limitations been discovered that justify continuing with Selenium?

If the options to a dropdown change while harness is selecting a value, it can get confused and not end up selecting the requested element

Pass { inBrowser: true } to make it run in the browser.

When performing a selection with findVisible or findVisibles, it will initially find some elements. An error can occur if the element(s) initially found never become visible - even though there might be some other matching elements on the page that do become visible.

The initial element selection should get re-ran until the timeout period expires.

Remove the 'ignore-certificate-errors' when running Chrome. We don't think it's needed anymore.

Update ElementProxy so you can call something like waitForClass('ready')

It would be convenient if given an ElementProxy, we could check if it is no longer pointing to an element in the dom.

If there are multiple elements that match the selector passed to findVisible, it might initially choose an invisible one, and wait for it to become visible. If the object never becomes visible, it will timeout and error.

In the case that the initial selector matches more than one element, and only one is visible, we should return that one.

It's using SIGTERM now by default, which makes Firefox think it crashed sometimes.

Allow it to connect to a new harness instance instead of having to close & re-open

When doing a waitFor and using a callback, the timeout logic doesn't get hit because the condition is only checked once rather than multiple times. We need to be able to timeout even if we're waiting on that callback.