queued 2026-09-24 19:44:24 · started 19:44:28 · finished 19:45:17 · duration 49s · target v1.0.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)
Activity replay 30 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.89s | goto http://127.0.0.1:8000/demo/freight/login/ | 141 ms |
| +1.03s | fill #username | 96 ms |
| +1.13s | fill #password | 32 ms |
| +1.16s | click #login-btn | 264 ms |
| +1.42s | wait_for_selector #signed-in-user | 132 ms |
| +1.55s | goto http://127.0.0.1:8000/demo/freight/ops/fleet/?region=california | 66 ms |
| +1.62s | wait_for_selector #fleet-table tbody tr | 71 ms |
| +1.85s | ⏱ wait for the truck to arrive | 46.09 s |
| +1.85s | wait_for_selector #fleet-events li[data-arrival='CA-2.3569648.4'] | 46.09 s |
| +48.06s | inner_text #fleet-events li[data-arrival='CA-2.3569648.4'] | 21 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-194428-r316/ |
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.89s] starting DEMO-019 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 141ms [timing] fill #username: 96ms [timing] fill #password: 32ms [timing] click #login-btn: 264ms [timing] wait_for_selector #signed-in-user: 132ms [test] [ 1.55s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/fleet/?region=california: 66ms [timing] wait_for_selector #fleet-table tbody tr: 71ms [test] [ 1.84s] screenshot: 01-fleet.png [test] [ 1.85s] CA-2 is due at Reno in 47s (arrival CA-2.3569648.4) [timing] wait_for_selector #fleet-events li[data-arrival='CA-2.3569648.4']: 46089ms [timing] wait for the truck to arrive: 46089ms [test] [ 48.06s] screenshot: 02-arrived.png [timing] inner_text #fleet-events li[data-arrival='CA-2.3569648.4']: 21ms [test] [ 48.08s] feed: 19:45:16 CA-2 arrived at Reno (on time) [test] [ 48.08s] PASSED [harness] security: 0 high, 1 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 |
|---|---|---|
| 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. |
| 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.