A collection of thoughts on software architecture, backend systems, and engineering challenges.
Second to last part of the playwright intro docs is about github actions integraiton.
I'll be using this page for testing: https://ocelotcodesystems.com/index.html
Before actually configuring github actions I wondered about how to parameterize the URL that the test would run against and decided to figure that out first.
...
Day 4 was supposed to be about grouping tests, but I got sidetracked debugging a resource issue. Still very valid experience, but now that it's done I can wrap up test grouping, then move on to CI integration and IDE integration.
Run everything:
...
Day 3 was about learning the different ways that tests can be grouped and selected for running.
At a glance everything was going great. I ran the tests in UI mode, immediately identified that I had missed a ".click()" on one of the tests, fixed it, ran it again.
I started suspecting resource constraints, so I limited the test to one simultaneous worker, like so:
...
The last remaining articles in Playwright's "Getting Started" section are
Running is very simple
...
Turns out the "GetByRole" function I saw in the example test is part of a whole API of element-getters:
CodeGen is a cool little tool that allows you to generate code by navigating around a website.
...
Here we go.
install it with `npm install playwright`,
...
In a backend I built for a webapp, the database has model/service/repo layers. The repository layer was meant to have some built-in security.
We still need that pattern of using a getter to check if the entity exists, and in fact I think we're going to have to use it both at the repo layer and at the service layer.
...