George S. Baugh
a1533a5228
Fix #4 more-or-less, not 100% coverage but good enough
|
vor 5 Jahren | |
|---|---|---|
| at | vor 5 Jahren | |
| bin | vor 5 Jahren | |
| lib | vor 5 Jahren | |
| t | vor 5 Jahren | |
| .gitignore | vor 5 Jahren | |
| Changes | vor 5 Jahren | |
| LICENSE | vor 5 Jahren | |
| MANIFEST.SKIP | vor 5 Jahren | |
| README.md | vor 5 Jahren | |
| api.json | vor 5 Jahren | |
| arg_order.js | vor 5 Jahren | |
| dist.ini | vor 5 Jahren | |
| example.pl | vor 5 Jahren | |
| package.json | vor 5 Jahren | |
| perlcriticrc | vor 5 Jahren | |
| tidyall.ini | vor 5 Jahren | |
| weaver.ini | vor 5 Jahren |
README.md
playwright-perl
Perl bindings for playwright, the amazing cross browser testing framework from Microsoft
Has this ever happened to you?
You're writing some acceptance test with Selenium::Remote:Driver, but you figure out selenium is a dead protocol? Finally, a solution!
Here's how it works
A little node webserver written in express is spun up which exposes the entire playwright API. We ensure the node deps are installed in a BEGIN block, and then spin up the proxy server. You then use playwright more or less as normal; see the POD in Playwright.pm for more details.
See example.pl for usage examples.
How2develop
npm i playwright express uuid yargs
perl -Ilib example.pl