queued 2026-09-24 19:46:19 · started 19:46:22 · finished 19:47:23 · duration 1m 01s · target v2.1.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)
Activity replay 31 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.98s | goto http://127.0.0.1:8000/demo/freight/login/ | 154 ms |
| +1.13s | fill #username | 144 ms |
| +1.27s | fill #password | 34 ms |
| +1.30s | click #login-btn | 138 ms |
| +1.45s | wait_for_selector #signed-in-user | 185 ms |
| +1.62s | goto http://127.0.0.1:8000/demo/freight/ops/fleet/?region=california | 85 ms |
| +1.72s | wait_for_selector #fleet-table tbody tr | 75 ms |
| +2.03s | ⏱ wait for the truck to arrive | 58.20 s |
| +2.03s | wait_for_selector #fleet-events li[data-arrival='CA-5.3555422.1'] | 58.20 s |
| +1:00.37 | inner_text #fleet-events li[data-arrival='CA-5.3555422.1'] | 20 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 |
| Folder | results/DEMO-019/20260924-194622-r325/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-019 browser=chromium headed=False timeout=240s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.97s] starting DEMO-019 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 154ms [timing] fill #username: 143ms [timing] fill #password: 34ms [timing] click #login-btn: 138ms [timing] wait_for_selector #signed-in-user: 185ms [test] [ 1.63s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/fleet/?region=california: 85ms [timing] wait_for_selector #fleet-table tbody tr: 75ms [test] [ 2.00s] screenshot: 01-fleet.png [test] [ 2.03s] CA-5 is due at San Luis Obispo in 59s (arrival CA-5.3555422.1) [timing] wait_for_selector #fleet-events li[data-arrival='CA-5.3555422.1']: 58200ms [timing] wait for the truck to arrive: 58200ms [test] [ 60.37s] screenshot: 02-arrived.png [timing] inner_text #fleet-events li[data-arrival='CA-5.3555422.1']: 20ms [test] [ 60.39s] feed: 19:47:21 CA-5 arrived at San Luis Obispo (on time) [test] [ 60.39s] PASSED [harness] security: 1 high, 3 medium, 1 low [harness] saved trace.zip [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.