queued 2026-09-24 18:54:37 · started 18:54:37 · finished 18:54:41 · duration 4s · target v1.1.0 · chromium · trigger: load
Step timings every page action is timed automatically
| at | step | took |
|---|---|---|
| +1.67s | ⏱ open the home page | 360 ms |
| +1.67s | goto http://127.0.0.1:8000/demo/freight/ | 360 ms |
| +2.02s | ⏱ track a shipment in transit | 385 ms |
| +2.03s | goto http://127.0.0.1:8000/demo/freight/track/ | 54 ms |
| +2.08s | fill #track-id | 64 ms |
| +2.15s | click #track-btn | 213 ms |
| +2.35s | wait_for_selector #track-result, #track-not-found | 55 ms |
| +2.41s | ⏱ track a delivered shipment | 452 ms |
| +2.42s | goto http://127.0.0.1:8000/demo/freight/track/ | 64 ms |
| +2.48s | fill #track-id | 42 ms |
| +2.52s | click #track-btn | 164 ms |
| +2.68s | wait_for_selector #track-result, #track-not-found | 180 ms |
| +2.86s | inner_text #track-status | 27 ms |
| +2.89s | ⏱ track an unknown number | 403 ms |
| +2.89s | goto http://127.0.0.1:8000/demo/freight/track/ | 80 ms |
| +2.97s | fill #track-id | 66 ms |
| +3.03s | click #track-btn | 157 ms |
| +3.19s | wait_for_selector #track-result, #track-not-found | 100 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-185437-r204/ |
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.67s] 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/: 53ms [timing] fill #track-id: 64ms [timing] click #track-btn: 213ms [timing] wait_for_selector #track-result, #track-not-found: 55ms [timing] track a shipment in transit: 385ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 64ms [timing] fill #track-id: 42ms [timing] click #track-btn: 164ms [timing] wait_for_selector #track-result, #track-not-found: 180ms [timing] track a delivered shipment: 452ms [timing] inner_text #track-status: 27ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 80ms [timing] fill #track-id: 66ms [timing] click #track-btn: 157ms [timing] wait_for_selector #track-result, #track-not-found: 100ms [timing] track an unknown number: 403ms [test] [ 3.31s] 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.