[atonse]

This looks awesome. Is the underlying recorded data available in an easy to parse format like JSON?

Would be quite powerful to do 90% of the work of transforming that recording to a puppeteer script to add to one’s test suite.

Speaking of which, what is the state of the art right now for browser automation scripts?

[bjarocki]

Thank you! And yes, it's all JSON. It's not super easy to read when you get all the data this way, though. I'm planning to add a web-based log reader to parse the logs and display them in the same way it's done in the extension.

Also, generating Cypress/Puppeteer/Playwright tests is on my to-do list. It should be fairly easy because all the data, including selectors, is already there. I wrote more about my plans here: https://jarocki.me/blog/monito

Regarding state of the art for browser automation scripts, I think the most popular tools are Cypress and Puppeteer. I'd like to get some feedback from QA folks, though.

[Xen0byte]

Hi, just to chip in because I read your request for feedback and also because I'm interested in seeing what Monito can do. I’ve been heading QA depts at large tech companies for a while now, and part of my job is to be up to speed with the latest tools and trends, and to write automation tools for various tech stack layers. To answer your question, my preferred front-end tool at the moment is Playwright (via C# binding). Playwright is the new kid on the block, but it has great potential; I’ve migrated all of our Selenium tests to it and I couldn’t be happier.

[bjarocki]

That's good to know, thank you! Is there anything I can do to make Monito worth adding to your toolset? Have you tried it? Thanks!