←back to thread

707 points namukang | 1 comments | | HN request time: 0.229s | source
Show context
sly010 ◴[] No.29257998[source]
Congrats, the demos look awesome! Having struggled with something like this in the past (for automated testing) I am always curious about how various solutions represent the "program" so its long term repeatable?

I often had to manually add branching on certain conditions (i.e login) or waiting for certain conditions (elements appearing) before proceeding.

I also often had to manually tweak selectors and even matches on html structurally (css selectors cannot select a parent element based on a matching content element).

Then there are the webpacked react sites that scramble css class names that change all the time.

Some of these things are super tedious to solve for even manually so I am just curious how no-code tools handle these?

replies(1): >>29258334 #
1. namukang ◴[] No.29258334[source]
Browserflow is more low-code than it is no-code since it has support for control flow statements like "If", "Else", etc. as well as being able to execute arbitrary Javascript on the page. The no-code approach of simply recording a flow works fine in many cases, but there are a lot of escape hatches if the flexibility is needed (e.g. waiting for an element to appear).

There's also support for a few unofficial pseudo-selectors (:contains and :has — see https://docs.browserflow.app/guides/selectors#writing-your-o...) to make selecting elements more reliable.

Hope that helps! Agreed that creating reliable automations for the Web is challenging and hopefully Browserflow will make it easier for many folks.