queued 2026-09-24 20:41:04 · started 20:41:06 · finished 20:41:09 · duration 3s · target v2.1.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)
Activity replay 2 frames, captured only while the page was actually changing — idle waits are skipped automatically
+0.00s
Step timings follows the replay — click a step to see it there
| at | step | took |
|---|---|---|
| +0.71s | goto http://127.0.0.1:8000/demo/freight/login/ | 226 ms |
| +0.94s | fill #username | 97 ms |
| +1.04s | fill #password | 120 ms |
| +1.16s | click #login-btn | 193 ms |
| +1.35s | wait_for_selector #signed-in-user | 223 ms |
| +1.57s | goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/ | 75 ms |
| +1.65s | ⏱ open the label (a new tab) | 214 ms |
| +1.65s | click #print-label | 91 ms |
| +1.92s | ⏱ scan the barcode | 11 ms |
| +1.94s | ⏱ download the PDF | 31 ms |
Times are when each step began, on the replay's clock. Add your own phases with
with ctx.timed("label"):.
Screenshots
Artifacts
| Run log | run.log |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Saved by the test | label-AF-100001.pdf |
| Folder | results/DEMO-024/20260924-204106-r346/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-024 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.71s] starting DEMO-024 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 226ms [timing] fill #username: 97ms [timing] fill #password: 120ms [timing] click #login-btn: 193ms [timing] wait_for_selector #signed-in-user: 223ms [test] [ 1.57s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/: 75ms [timing] click #print-label: 91ms [timing] open the label (a new tab): 214ms [test] [ 1.86s] the label opened in a new tab: http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/label/ [timing] scan the barcode: 11ms [test] [ 1.93s] the barcode reads 'AF-100001' [timing] download the PDF: 31ms [test] [ 1.97s] the PDF (2774 bytes) carries the same barcode [test] [ 2.29s] PASSED [harness] security: 1 high, 3 medium, 1 low [harness] saved trace.zip [harness] saved video.webm [harness] result: passed
Security observations what the browser noticed while this ran — not a penetration test
| Severity | Finding | What to do |
|---|---|---|
| high | The page requested resources from other hosts Requests went to: analytics.acme-metrics.invalid (3). On an air-gapped network these cannot succeed -- so the page is either broken or waiting on a timeout -- and each one is a path by which data could leave the enclave. |
Vendor the resource locally, or remove the reference. This is worth chasing even when the page still appears to work. |
| medium | The application is served over plain HTTP http://127.0.0.1:8000/demo/ is not HTTPS, so anything typed into it travels the network in the clear and can be modified in transit. |
On an isolated lab network this may be a deliberate choice -- if so, note it and move on. Anywhere else, terminate TLS in front of the application. |
| medium | Missing Content-Security-Policy Without it, an injected script can run with the page's full privileges. This is the single most effective header against XSS. |
Set the Content-Security-Policy response header on the application or its reverse proxy. |
| medium | Missing X-Frame-Options (or CSP frame-ancestors) Without it, another site can embed this page invisibly and trick a user into clicking things (clickjacking). |
Set the X-Frame-Options (or CSP frame-ancestors) response header on the application or its reverse proxy. |
| low | Response advertises software version (server) server: pw-testhub -- this tells an attacker exactly what to look up known vulnerabilities for. |
Suppress or blank the server header at the proxy. |
| info | Cookie 'csrftoken' is readable by JavaScript (expected) This looks like a CSRF token, which the page's own JavaScript has to read in order to send it back. HttpOnly would break that. Nothing to do -- listed so you know it was checked and not missed. |
No action. Do check that SESSION cookies are HttpOnly. |
All of these appear together on the Security page.