Writing
Articles
Notes on test automation, reporting and the constraints of running suites on infrastructure you do not control. Every piece also comes as an offline copy: one file with the images, fonts and styles inlined, which opens on a machine with no network at all.
- 6 min readen
The report has to work when the dashboard cannot
An honest survey of test reporting for environments that cannot reach a cloud service: what the framework report, Allure, self-hosted TestOps-class tools and Grafana each give you, where each one stops, and what a report must carry to stand on its own.
- 5 min readen
The build has to work on a machine that cannot download anything
Where the network boundary belongs in an offline pipeline, the three ways to vendor Node dependencies and when each one fits, and how to verify that an install genuinely never reaches a registry.
- 6 min readen
Everything that breaks the first time you unplug
A catalogue of what actually fails when a working suite is moved into a closed network: 64 MB of shared memory, fonts from a CDN, revocation checks, telemetry, clock drift - and the timeouts they all turn into.
- 5 min readen
The version you are on is the version you are stuck with
Playwright ships monthly while a transfer into a closed environment takes weeks: how to choose an upgrade cadence, what breaks when you jump several versions at once, and how to make a rollback a path change rather than another transfer.
- 10 min readen
One tarball is a procedure, twenty is a problem
Serving Playwright browser archives from your own artifact repository once copying tarballs stops scaling: the layout the installer expects, and what it costs to keep the mirror current.
- 12 min readen
The browsers have to get there somehow
A complete procedure for installing Playwright browsers on a machine with no route to the internet: what to fetch, how to move it, how to verify it, and how to carry several versions so a rollback is not another transfer.
- 25 min readen
The tests nobody on the outside will ever see
Automation, reporting and running test suites where there is no route to the internet: hermetic suites, self-contained reports, and who else ends up holding your test data.