queued 2026-09-24 18:54:30 · started 18:54:30 · finished 18:54:34 · duration 3s · target v1.1.0 · chromium · trigger: load
Step timings every page action is timed automatically
| at | step | took |
|---|---|---|
| +1.41s | ⏱ open the home page | 223 ms |
| +1.41s | goto http://127.0.0.1:8000/demo/freight/ | 223 ms |
| +1.62s | ⏱ track a shipment in transit | 498 ms |
| +1.62s | goto http://127.0.0.1:8000/demo/freight/track/ | 48 ms |
| +1.68s | fill #track-id | 114 ms |
| +1.79s | click #track-btn | 248 ms |
| +2.03s | wait_for_selector #track-result, #track-not-found | 88 ms |
| +2.13s | ⏱ track a delivered shipment | 431 ms |
| +2.13s | goto http://127.0.0.1:8000/demo/freight/track/ | 72 ms |
| +2.19s | fill #track-id | 46 ms |
| +2.25s | click #track-btn | 224 ms |
| +2.47s | wait_for_selector #track-result, #track-not-found | 88 ms |
| +2.56s | inner_text #track-status | 75 ms |
| +2.63s | ⏱ track an unknown number | 357 ms |
| +2.63s | goto http://127.0.0.1:8000/demo/freight/track/ | 76 ms |
| +2.71s | fill #track-id | 50 ms |
| +2.76s | click #track-btn | 192 ms |
| +2.95s | wait_for_selector #track-result, #track-not-found | 39 ms |
Times are when each step began, on the replay's clock. Add your own phases with
with ctx.timed("label"):.
Screenshots
No screenshots (use ctx.screenshot("name") in the test).
Artifacts
| Run log | run.log |
| Result JSON | result.json |
| Folder | results/DEMO-018/20260924-185430-r194/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-018 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 1.40s] starting DEMO-018 [timing] goto http://127.0.0.1:8000/demo/freight/: 223ms [timing] open the home page: 223ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 48ms [timing] fill #track-id: 114ms [timing] click #track-btn: 248ms [timing] wait_for_selector #track-result, #track-not-found: 88ms [timing] track a shipment in transit: 498ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 71ms [timing] fill #track-id: 46ms [timing] click #track-btn: 224ms [timing] wait_for_selector #track-result, #track-not-found: 89ms [timing] track a delivered shipment: 431ms [timing] inner_text #track-status: 75ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 76ms [timing] fill #track-id: 50ms [timing] click #track-btn: 192ms [timing] wait_for_selector #track-result, #track-not-found: 39ms [timing] track an unknown number: 357ms [test] [ 3.00s] PASSED [harness] security: 0 high, 1 medium, 1 low [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.