queued 2026-09-24 19:46:19 · started 19:46:19 · finished 19:46:24 · duration 4s · target v2.1.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)
Activity replay 6 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.86s | goto http://127.0.0.1:8000/demo/freight/login/ | 136 ms |
| +1.01s | fill #username | 142 ms |
| +1.14s | fill #password | 28 ms |
| +1.18s | click #login-btn | 131 ms |
| +1.31s | wait_for_selector #signed-in-user | 191 ms |
| +1.50s | goto http://127.0.0.1:8000/demo/freight/ops/docks/ | 88 ms |
| +1.59s | get_attribute #arrivals .dock-card[data-hazardous='1'] | 40 ms |
| +1.63s | get_attribute #arrivals .dock-card[data-heavy='1'][data-hazardous='0'] | 12 ms |
| +1.64s | get_attribute #arrivals .dock-card[data-heavy='0'][data-hazardous='0'] | 10 ms |
| +1.65s | ⏱ drag a normal load to Door 3, 09:00 | 241 ms |
| +1.65s | drag_and_drop .dock-card[data-arrival='IN-0924-03'] | 121 ms |
| +1.77s | wait_for_selector td[data-cell='D3|09:00'] .dock-card[data-arrival='IN-0924-03'] | 120 ms |
| +1.89s | drag_and_drop .dock-card[data-arrival='IN-0924-01'] | 119 ms |
| +1.89s | ⏱ try hazardous goods at Door 1 | 168 ms |
| +2.01s | wait_for_selector #dock-error:not([hidden]) | 49 ms |
| +2.06s | inner_text #dock-error | 54 ms |
| +2.57s | ⏱ drag hazardous goods to Door 4 (hazmat) | 270 ms |
| +2.58s | drag_and_drop .dock-card[data-arrival='IN-0924-01'] | 104 ms |
| +2.67s | wait_for_selector td[data-cell='D4|10:00'] .dock-card[data-arrival='IN-0924-01'] | 165 ms |
| +2.84s | ⏱ drag a heavy load to a forklift door | 327 ms |
| +2.85s | drag_and_drop .dock-card[data-arrival='IN-0924-02'] | 134 ms |
| +2.98s | wait_for_selector td[data-cell='D1|11:00'] .dock-card[data-arrival='IN-0924-02'] | 193 ms |
| +3.17s | reload | 103 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-021/20260924-194619-r327/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-021 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.87s] starting DEMO-021 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 136ms [timing] fill #username: 142ms [timing] fill #password: 28ms [timing] click #login-btn: 131ms [timing] wait_for_selector #signed-in-user: 191ms [test] [ 1.50s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/docks/: 88ms [timing] get_attribute #arrivals .dock-card[data-hazardous='1']: 40ms [timing] get_attribute #arrivals .dock-card[data-heavy='1'][data-hazardous='0']: 12ms [timing] get_attribute #arrivals .dock-card[data-heavy='0'][data-hazardous='0']: 10ms [test] [ 1.65s] hazmat IN-0924-01, heavy IN-0924-02, normal IN-0924-03 [timing] drag_and_drop .dock-card[data-arrival='IN-0924-03']: 121ms [timing] wait_for_selector td[data-cell='D3|09:00'] .dock-card[data-arrival='IN-0924-03']: 120ms [timing] drag a normal load to Door 3, 09:00: 241ms [timing] drag_and_drop .dock-card[data-arrival='IN-0924-01']: 119ms [timing] wait_for_selector #dock-error:not([hidden]): 49ms [timing] try hazardous goods at Door 1: 168ms [timing] inner_text #dock-error: 54ms [test] [ 2.46s] screenshot: 01-refused.png [timing] drag_and_drop .dock-card[data-arrival='IN-0924-01']: 104ms [timing] wait_for_selector td[data-cell='D4|10:00'] .dock-card[data-arrival='IN-0924-01']: 165ms [timing] drag hazardous goods to Door 4 (hazmat): 270ms [timing] drag_and_drop .dock-card[data-arrival='IN-0924-02']: 134ms [timing] wait_for_selector td[data-cell='D1|11:00'] .dock-card[data-arrival='IN-0924-02']: 193ms [timing] drag a heavy load to a forklift door: 327ms [timing] reload: 103ms [test] [ 3.53s] screenshot: 02-scheduled.png [test] [ 3.53s] 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 (7). 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.