queued 2026-09-24 19:47:27 · started 19:47:29 · finished 19:48:11 · duration 41s · target v3.0.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)
Activity replay 29 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 |
|---|---|---|
| +1.02s | goto http://127.0.0.1:8000/demo/freight/login/ | 125 ms |
| +1.15s | fill #username | 114 ms |
| +1.26s | fill #password | 88 ms |
| +1.35s | click #login-btn | 145 ms |
| +1.50s | wait_for_selector #signed-in-user | 195 ms |
| +1.69s | goto http://127.0.0.1:8000/demo/freight/ops/fleet/?region=california | 93 ms |
| +1.78s | wait_for_selector #fleet-table tbody tr | 70 ms |
| +2.04s | ⏱ wait for the truck to arrive | 38.14 s |
| +2.04s | wait_for_selector #fleet-events li[data-arrival='CA-4.5799989.5'] | 38.14 s |
| +40.30s | inner_text #fleet-events li[data-arrival='CA-4.5799989.5'] | 18 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-194729-r328/ |
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] [ 1.02s] starting DEMO-019 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 125ms [timing] fill #username: 115ms [timing] fill #password: 88ms [timing] click #login-btn: 145ms [timing] wait_for_selector #signed-in-user: 195ms [test] [ 1.69s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/fleet/?region=california: 93ms [timing] wait_for_selector #fleet-table tbody tr: 69ms [test] [ 2.02s] screenshot: 01-fleet.png [test] [ 2.04s] CA-4 is due at Ukiah in 37s (arrival CA-4.5799989.5) [timing] wait_for_selector #fleet-events li[data-arrival='CA-4.5799989.5']: 38137ms [timing] wait for the truck to arrive: 38137ms [test] [ 40.31s] screenshot: 02-arrived.png [timing] inner_text #fleet-events li[data-arrival='CA-4.5799989.5']: 18ms [test] [ 40.32s] feed: 19:48:08 CA-4 arrived at Ukiah (on time) [test] [ 40.32s] 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.