queued 2026-09-24 22:04:21 · started 22:04:21 · finished 22:04:24 · duration 3s · target v2.1.0 · chromium · trigger: group · batch: group: Freight smoke
Activity replay 3 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.79s | goto http://127.0.0.1:8000/demo/freight/ | 316 ms |
| +1.11s | inner_text #hero-title | 114 ms |
| +1.21s | get_attribute meta[name="app-version"] | 66 ms |
| +1.52s | goto http://127.0.0.1:8000/demo/freight/track/ | 87 ms |
| +1.52s | ⏱ track a shipment in transit | 406 ms |
| +1.61s | fill #track-id | 55 ms |
| +1.67s | click #track-btn | 170 ms |
| +1.84s | wait_for_selector #track-result, #track-not-found | 93 ms |
| +1.94s | inner_text #track-status | 14 ms |
| +1.95s | inner_text #track-destination | 10 ms |
| +2.17s | ⏱ track an unknown number | 321 ms |
| +2.17s | goto http://127.0.0.1:8000/demo/freight/track/ | 109 ms |
| +2.28s | fill #track-id | 43 ms |
| +2.32s | click #track-btn | 113 ms |
| +2.43s | wait_for_selector #track-result, #track-not-found | 57 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-010/20260924-220421-r351/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-010 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.79s] starting DEMO-010 [timing] goto http://127.0.0.1:8000/demo/freight/: 315ms [timing] inner_text #hero-title: 114ms [timing] get_attribute meta[name="app-version"]: 66ms [test] [ 1.28s] Acme Freight says it is release 2.1.0 [test] [ 1.53s] screenshot: 01-home.png [timing] goto http://127.0.0.1:8000/demo/freight/track/: 87ms [timing] fill #track-id: 55ms [timing] click #track-btn: 170ms [timing] wait_for_selector #track-result, #track-not-found: 93ms [timing] track a shipment in transit: 406ms [timing] inner_text #track-status: 14ms [timing] inner_text #track-destination: 10ms [test] [ 2.17s] screenshot: 02-tracking.png [timing] goto http://127.0.0.1:8000/demo/freight/track/: 109ms [timing] fill #track-id: 43ms [timing] click #track-btn: 113ms [timing] wait_for_selector #track-result, #track-not-found: 57ms [timing] track an unknown number: 321ms [test] [ 2.50s] 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 (5). 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.