queued 2026-09-24 18:55:20 · started 18:55:20 · finished 18:55:24 · duration 3s · target v1.1.0 · chromium · trigger: load
Step timings every page action is timed automatically
| at | step | took |
|---|---|---|
| +1.42s | ⏱ open the home page | 380 ms |
| +1.42s | goto http://127.0.0.1:8000/demo/freight/ | 380 ms |
| +1.80s | ⏱ track a shipment in transit | 498 ms |
| +1.80s | goto http://127.0.0.1:8000/demo/freight/track/ | 57 ms |
| +1.86s | fill #track-id | 72 ms |
| +1.93s | click #track-btn | 299 ms |
| +2.23s | wait_for_selector #track-result, #track-not-found | 69 ms |
| +2.30s | goto http://127.0.0.1:8000/demo/freight/track/ | 83 ms |
| +2.30s | ⏱ track a delivered shipment | 358 ms |
| +2.38s | fill #track-id | 35 ms |
| +2.41s | click #track-btn | 137 ms |
| +2.56s | wait_for_selector #track-result, #track-not-found | 102 ms |
| +2.66s | inner_text #track-status | 20 ms |
| +2.67s | ⏱ track an unknown number | 439 ms |
| +2.67s | goto http://127.0.0.1:8000/demo/freight/track/ | 66 ms |
| +2.74s | fill #track-id | 39 ms |
| +2.78s | click #track-btn | 197 ms |
| +2.97s | wait_for_selector #track-result, #track-not-found | 137 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-185520-r267/ |
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.42s] starting DEMO-018 [timing] goto http://127.0.0.1:8000/demo/freight/: 380ms [timing] open the home page: 380ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 57ms [timing] fill #track-id: 72ms [timing] click #track-btn: 299ms [timing] wait_for_selector #track-result, #track-not-found: 69ms [timing] track a shipment in transit: 498ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 83ms [timing] fill #track-id: 35ms [timing] click #track-btn: 137ms [timing] wait_for_selector #track-result, #track-not-found: 102ms [timing] track a delivered shipment: 358ms [timing] inner_text #track-status: 20ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 66ms [timing] fill #track-id: 39ms [timing] click #track-btn: 197ms [timing] wait_for_selector #track-result, #track-not-found: 137ms [timing] track an unknown number: 439ms [test] [ 3.18s] 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.