I also noticed it a few days ago.
It was a pleasant surprise.
But it sure feels like a first version.
The good parts:
It's easy to record a short script.
You can run that script directly in your own Chrome browser.
The recorded script is saved and can even be exported as a Puppeteer js file.
The not-so-good parts:
The lack of artifacts (detailed logs, screenshots and video).
You can't run the scripts from your CI/CD system.
No options to add advanced actions, logic, reusable components, variables or assertions.
No possibility to collaborate with other team members.
Puppeteer has very limited cross-browser support, you can't run that test on Safari (which has 19% market share).
My two cents:
If you're working on a weekend project, it's a decent way to test if it's working correctly in Chrome.
As for testing complex flows, it's not going to cut it.
Disclaimer:
As someone working at Endtest, I know that a useful test automation tool needs a lot more than a record and playback feature.
I also noticed it a few days ago.
It was a pleasant surprise.
But it sure feels like a first version.
The good parts:
The not-so-good parts:
My two cents:
If you're working on a weekend project, it's a decent way to test if it's working correctly in Chrome.
As for testing complex flows, it's not going to cut it.
Disclaimer:
As someone working at Endtest, I know that a useful test automation tool needs a lot more than a record and playback feature.
Totally is a beta feature for now, but pretty sure Chrome will make it better over time.
Technically you could get a screencap artifact from the performance tab.
And when running puppeteer include that as in the CI/CD.
But get your points, as this is very limited and more a workaround than it could be.
Let's hope they keep improving this.