Hacker News Reader

Comment by nikanj | Hacker News Reader

Edge can't be automated via COM the same way IE could. I wonder what MS is offering as an upgrade path

Edge supports WebDriver: https://docs.microsoft.com/en-us/microsoft-edge/webdriver-ch...

Looks like the customer would have to download the Edge driver from Microsoft, picking the right version (and supposedly update the drivers as Edge auto-updates).

That's a complete non-starter, compared to automating IE that just requires our .exe to create an IE object via CoCreateInstance(CLSID_InternetExplorerMedium ...), and no additional installation by the customer organization.

The desktop application is deprecated. The guts of the Trident engine will live on forever… probably.

FireFox?

Do you have any links to documentation for automating FF?

Some options for automating website tests in Firefox:

WebDriver: https://developer.mozilla.org/en-US/docs/Web/WebDriver

Marionette: https://firefox-source-docs.mozilla.org/testing/marionette/I...

Puppeteer: https://www.infoq.com/news/2020/04/puppeteer-3-firefox-suppo...

I haven't used these tools, so I don't know which is "best" or why so many different tools are needed. :)

I don’t want to run tests, I want to drive the browser for the customer. I guess it’s time to learn chrome extensions

Mozilla uses Marionette to automate its own browser UI testing (not just clicking on web pages).

For better or worse (better, I'd argue), I don't think browsers want you to drive the browser for the customer. My takeaway from most modern browser security developments is that if you can't do it with the standard APIs, you aren't supposed to be doing it.

Microsoft Power Automate

Reply on news.ycombinator.com