[4.x] record() method

[gpibarra]

I thought the presentation of the new browser tests at Laracon was amazing!
I had previously seen a similar idea here: https://github.com/glhd/dawn — but it remained just a WIP/PoC.

While looking at the tinker() and debug() methods, I was reminded of a method called magic() (maybe record() would be a better name) that I saw a while ago in this project: https://github.com/magic-test/magic-test-laravel.
The idea is to pause the test execution, show the browser, and record mouse and keyboard interactions — then reconstruct the syntax automatically as a test.

It would be super interesting to have something like that, or perhaps take inspiration from this approach: https://github.com/mpociot/laravel-testtools, which relied on a Chrome extension.

[mauricekindermann]

☝️ yes this x 1000. In theory this could be built as a chrome extension, but building it right into Pest would be elite and make the 'I don't write tests" mindset almost impossible.

I remember finding those exact package links last year and wishing both Dusk was faster and those packages were maintained.

Many years ago I used Ghost Inspector to do some simple frontend webhook based browser testing, and they had an extension at the time to record your session to turn it into a working test.

Injecting a little recorder script into Pest itself, then returning that would be killer.

Imagine being able to do:

php artisan test tests/Browser/NewTest.php --record

Right now I'm having issues with the Stripe payment iframe - the Dusk test I had using input[name="cardNumber"] didn't work immediately, so now I need to figure out what would make Pest not see that element. If I could record, and the internal script could just make those references for me, I'd be done already.