|
|
%!s(int64=5) %!d(string=hai) anos | |
|---|---|---|
| bin | %!s(int64=5) %!d(string=hai) anos | |
| lib | %!s(int64=5) %!d(string=hai) anos | |
| .gitignore | %!s(int64=5) %!d(string=hai) anos | |
| Changes | %!s(int64=5) %!d(string=hai) anos | |
| LICENSE | %!s(int64=5) %!d(string=hai) anos | |
| MANIFEST.SKIP | %!s(int64=5) %!d(string=hai) anos | |
| README.md | %!s(int64=5) %!d(string=hai) anos | |
| dist.ini | %!s(int64=5) %!d(string=hai) anos | |
| perlcriticrc | %!s(int64=5) %!d(string=hai) anos | |
| tidyall.ini | %!s(int64=5) %!d(string=hai) anos | |
| weaver.ini | %!s(int64=5) %!d(string=hai) anos |
Perl bindings for [playwright][pw]
You're writing some acceptance test with [Selenium::Remote:Driver][srd], but you figure out selenium is a dead protocol? Finally, a solution!
A little node webserver written in [express][xp] is spun up which exposes the entire playwright API. You build a bunch of little actions to do much like action chains in Selenium, and then make 'em go whir.
The best way to do this is probably using [Promise::XS][xs].
npm i playwright express perl -Ilib example.pl