headless-recorder

https://github.com/checkly/headless-recorder - got ~15k GitHub stars. - AWS copied it. - We deprecated it as better stuff came on the market with @playwright/test's codegen. But I did code the initial version in a weekend. Was called Puppeteer Recorder then.

Checkly CTO and founder here. Thanks for trying Checkly. Just looking at Preflight, I think the audience might be different. Where we — Checkly — focus heavily on "code first / developer first", Preflight seems to target no/low code. For us, code-first / dev-first means we directly integrate with popular JS frameworks (like Playwright and Puppeteer), allow you to code any setup / teardown scripts in NodeJs and generally want you to treat your testing and monitoring setup "as code". So, TLDR is that I would 100% give Preflight a try and see if it matches your workflow. Always choose the best tool for your problem! P.S. we do help with generating test scripts with our Chrome extension https://github.com/checkly/headless-recorder

Check out Headless Recorder. It records browser interactions and generates Puppeteer and Playwright scripts. https://github.com/checkly/headless-recorder

> Oh @awscloud I really do :Two hearts: you! But next time you fork my OS project https://github.com/checkly/headless-recorder and present it as your new service, give the maintainers a short "nice job, kids" or something. Not necessary as per the APLv2 license, but still, ya know? He is only nicely and asking for recognition/attribution while acknowledging that it's not required per licence. I don't know why people have to take sides or be angry about it. Just as amazon was free to take his project and make it their own, he is Free to mention the fact that someone is indeed selling his work without even giving an open mention.

So it looks like this keys off of class selectors. Anyone know of a solution for cases where you have dynamic selector names? Frameworks like next.js (using styled-jsx) add random strings to class names at build to create classname uniqueness [0]. [0]: https://github.com/vercel/styled-jsx#how-it-works EDIT: Looks like one solution is to put an ID on the elements you're interacting with. [1] [1]: https://github.com/checkly/headless-recorder/issues/32

Hey, here is a basic & open source recorder for Puppeteer: https://github.com/checkly/puppeteer-recorder from the same team (disclaimer I'm co-founder of Checkly)

Checkly | Full Stack JavaScript Engineer | Berlin, Germany OR Remote | https://checklyhq.com/ Checkly is an API and site transaction monitoring SAAS for modern DevOps teams. We combine in-depth API monitoring with scripted browser transactions using Puppeteer. Our goal is to be the default active monitoring platform for developers. We’re a young company but growing rapidly with some exciting customers joining us every month. You’ll work on our fronted, backend and infra. We also build & maintain a popular (6.5k stars) open source browser extension https://github.com/checkly/puppeteer-recorder Here is the open role: - Full Stack Javascript Engineer: https://checklyhq.com/jobs/full-stack-javascript-engineer-20... Tech Stack: Node.js, Vue.js, Postgres, Heroku, AWS Lambda, SNS, S3 and SQS. Please email your resume & motivation to: jobs@checkl

Httpie - basically a nicer cUrl. Adding json and headers is super simple. https://httpie.org Puppeteer Recorder - tooting my own horn, but is a Chrome extension that records Puppeteer scripts. https://github.com/checkly/puppeteer-recorder