// blog.md
Field notes from someone who tests living.
- 30
- when it matters
- markdown + vim
// post 030
featured · latest The Internet Runs on Remote Work. Your CEO Says It Doesn't Work
The largest engineering projects in history are distributed by design, yet executives keep insisting distributed work fails. What the RTO research, the real estate money trail, and one Australian policy contradiction actually show.
#RemoteWork
#RegionalAustralia
#OpenSource
#TestAutomation
#FutureOfWork
cat internet-runs-on-remote-work.md
$ cat internet-runs-on-remote-work.md
# # The internet runs on remote work
Your CEO's RTO memo reached you through
software built by people who have never
shared an office.
Linux: 2,134 devs, 1,780+ orgs, one release.
Kubernetes: 88,000 contributors, 44 countries.
// published
Where Slack Put AI Agents in Its E2E Testing Stack Strategy Slack ran more than 200 end-to-end workflows through AI agents to map where intent-driven tests beat brittle scripts and where the price per run keeps scripts in charge. Your Cucumber Suite Is a Test Script in a Plain-English Costume Strategy The value in BDD lives in the conversation before the code, not the .feature file; a Cucumber suite that skips that conversation becomes a brittle test script wearing plain English. Two k6 Load Models Measure Two Different Systems Strategy A closed-model k6 test eases off the moment the server slows; an open-model test holds the request rate and shows you the tail your users will hit. Your CI's AI agent was running on a standing credential Tools Running Copilot CLI in GitHub Actions used to need a stored personal access token; the CLI now reads the run built-in GITHUB_TOKEN, a credential that expires with the job. Let a flake-rate metric build your quarantine list Practice A hand-kept flaky-test list goes stale the day you save it. Score each test flake rate in Prometheus and a query keeps the quarantine list current for you. k6 2.1 Ships a Feature-Flag System for Experimental Behavior Tools k6 2.1 adds a feature-flag system: opt into experimental behavior with --features, list what exists with k6 features, and switch trend metrics to native Prometheus histograms. Playwright 1.61 Tests Passkey Logins Without a Hardware Key Tools Playwright 1.61 ships a virtual authenticator that registers passkeys in-test, so the passkey login button gets E2E coverage without a security key. Checkout v7 refuses the pwn request by default Tools actions/checkout v7 refuses to fetch fork pull request code under pull_request_target, closing the most copied half of the pwn request attack. A pull request title ran shell commands in Nx's pipeline Practice A PR title carried shell commands, a run step echoed it, and the runner obeyed. Bind untrusted input to an env var and quote it. Your API requests belong in Git, not Postman's cloud Tools A private Postman collection does two jobs badly. Send the quick check to cURL and a .http file, the endpoint tests to Playwright, and let git hold both. Stop seeding your Playwright suite from the login form Practice Drive the login form to seed every test and one selector change reddens the whole suite. Authenticate through the API and keep one test on the form. Your coverage gate rewards tests that assert nothing Strategy Line coverage counts execution, not checking. A test that runs your code and asserts nothing still passes an 85 percent gate. Five steps to a GitHub merge queue that does not stall Practice A merge queue tests each PR against the ones ahead of it before it lands. Five setup steps keep it moving instead of stalling the day you turn it on. GitLab 19.0 moves the secrets manager into the pipeline Tools GitLab 19.0 bundles OpenBao as a native secrets store, so you stop running a standalone Vault just to feed your pipelines. Where Test Health Belongs: CI Logs or an Observability Backend Strategy Your suite emits pass rate and flake count every run, then buries them in a CI log nobody scrolls; export them over OTLP and a dashboard catches the rot. Retrying a flaky test deletes the evidence of a real bug Strategy A bug that fails one run in four passes CI 99.6 percent of the time under three retries. Quarantine the test instead and keep the signal. Three caching changes that take 80% off a GitHub Actions build Practice A cached ~/.npm drops a cold Node install from four minutes to thirty seconds, and two more cache changes take the rest of the pipeline down with it. My resume site ships behind 460 tests Meta I set the direction and Claude Code wrote the code and the tests; 247 unit tests and 213 browser tests are how I trust a site I never hand-wrote. GitHub Actions parallel steps and the matrix jobs you can retire Tools Three matrix jobs for lint, type-check, and unit tests pay three runner boots and an artifact handoff for concurrency that parallel steps fold back into one job. Contract Testing vs End-to-End: Where Integration Bugs Belong Strategy A contract test catches a renamed field in seconds; a 20-minute E2E suite catches it after booting six services. Put each test where it earns its minutes. k6 Script Authoring calibrates load tests to live traffic Tools Grafana Assistant reads your telemetry, finds endpoints by real RPS and p95, and generates a k6 script that inherits that profile. When AI can write every test, what ships to CI is the job Strategy AI-generated Playwright tests flake under 1.5%. The new problem is test explosion, and coverage intent is still yours to define. One click to fix a failing GitHub Actions run Tools Fix with Copilot puts a cloud agent on the failure: it investigates, pushes a fix, reruns CI, and tags you for review. 90% use AI in the IDE; the pipeline is another story Strategy JetBrains data: daily AI in the editor, almost none in CI/CD. The trust gap closes when AI reduces noise instead of adding it. Bitbucket Agentic Pipelines automates the chores Tools Define an agent block in bitbucket-pipelines.yml, scope it, tie it to an event. It drafts the docs and the coverage gaps; you review. Playwright 1.59 turns failures into reviewable evidence Tools The 1.59 agents plus screencast and browser.bind shift your job from chasing selectors to reviewing what the Healer did. k6 2.0 moves load-test authoring into the CLI Tools Grafana previewed k6 2.0 at GrafanaCON 2026: AI authoring in the CLI, an MCP server, and a Playwright-to-k6 converter. The locator tax nobody puts in the budget Strategy Broken-test triage is a staffing decision disguised as a process one. Here is the cost, and where AI self-healing pays it back. Playwright agents and the new QA skills gap Tools Playwright v1.56 put a Planner, Generator, and Healer in the test runner. The interesting part is what it asks of the engineers who own the suite.