TestRail Perl API

George S. Baugh 977be40cb6 skeleton of module & beginning of app server 5 anni fa
bin 977be40cb6 skeleton of module & beginning of app server 5 anni fa
lib 977be40cb6 skeleton of module & beginning of app server 5 anni fa
.gitignore 977be40cb6 skeleton of module & beginning of app server 5 anni fa
Changes 977be40cb6 skeleton of module & beginning of app server 5 anni fa
LICENSE 10209758b6 update xright 5 anni fa
MANIFEST.SKIP 977be40cb6 skeleton of module & beginning of app server 5 anni fa
README.md 977be40cb6 skeleton of module & beginning of app server 5 anni fa
dist.ini 977be40cb6 skeleton of module & beginning of app server 5 anni fa
perlcriticrc 977be40cb6 skeleton of module & beginning of app server 5 anni fa
tidyall.ini 977be40cb6 skeleton of module & beginning of app server 5 anni fa
weaver.ini 977be40cb6 skeleton of module & beginning of app server 5 anni fa

README.md

playwright-perl

Perl bindings for [playwright][pw]

Has this ever happened to you?

You're writing some acceptance test with [Selenium::Remote:Driver][srd], but you figure out selenium is a dead protocol? Finally, a solution!

Here's how it works

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].

How2develop

npm i playwright express perl -Ilib example.pl