queued 2026-09-24 18:51:49 · started 18:51:49 · finished 18:51:52 · duration 3s · target v1.0.0 · chromium · trigger: load
Step timings every page action is timed automatically
| at | step | took |
|---|---|---|
| +1.34s | ⏱ open the home page | 360 ms |
| +1.34s | goto http://127.0.0.1:8000/demo/freight/ | 360 ms |
| +1.70s | ⏱ track a shipment in transit | 591 ms |
| +1.70s | goto http://127.0.0.1:8000/demo/freight/track/ | 91 ms |
| +1.79s | fill #track-id | 68 ms |
| +1.86s | click #track-btn | 371 ms |
| +2.23s | wait_for_selector #track-result, #track-not-found | 61 ms |
| +2.29s | ⏱ track a delivered shipment | 494 ms |
| +2.29s | goto http://127.0.0.1:8000/demo/freight/track/ | 63 ms |
| +2.35s | fill #track-id | 74 ms |
| +2.42s | click #track-btn | 278 ms |
| +2.70s | wait_for_selector #track-result, #track-not-found | 79 ms |
| +2.78s | inner_text #track-status | 22 ms |
| +2.80s | ⏱ track an unknown number | 381 ms |
| +2.80s | goto http://127.0.0.1:8000/demo/freight/track/ | 26 ms |
| +2.83s | fill #track-id | 25 ms |
| +2.86s | click #track-btn | 302 ms |
| +3.15s | wait_for_selector #track-result, #track-not-found | 27 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-185149-r141/ |
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.34s] starting DEMO-018 [timing] goto http://127.0.0.1:8000/demo/freight/: 360ms [timing] open the home page: 360ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 91ms [timing] fill #track-id: 68ms [timing] click #track-btn: 371ms [timing] wait_for_selector #track-result, #track-not-found: 61ms [timing] track a shipment in transit: 591ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 63ms [timing] fill #track-id: 74ms [timing] click #track-btn: 278ms [timing] wait_for_selector #track-result, #track-not-found: 79ms [timing] track a delivered shipment: 494ms [timing] inner_text #track-status: 22ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 26ms [timing] fill #track-id: 25ms [timing] click #track-btn: 302ms [timing] wait_for_selector #track-result, #track-not-found: 27ms [timing] track an unknown number: 381ms [test] [ 3.20s] 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.