queued 2026-09-24 18:50:37 · started 18:50:37 · finished 18:50:41 · duration 3s · target v1.0.0 · chromium · trigger: load
Step timings every page action is timed automatically
| at | step | took |
|---|---|---|
| +1.31s | ⏱ open the home page | 365 ms |
| +1.31s | goto http://127.0.0.1:8000/demo/freight/ | 365 ms |
| +1.68s | ⏱ track a shipment in transit | 560 ms |
| +1.69s | goto http://127.0.0.1:8000/demo/freight/track/ | 65 ms |
| +1.75s | fill #track-id | 112 ms |
| +1.86s | click #track-btn | 290 ms |
| +2.15s | wait_for_selector #track-result, #track-not-found | 93 ms |
| +2.24s | ⏱ track a delivered shipment | 627 ms |
| +2.24s | goto http://127.0.0.1:8000/demo/freight/track/ | 197 ms |
| +2.44s | fill #track-id | 55 ms |
| +2.50s | click #track-btn | 304 ms |
| +2.80s | wait_for_selector #track-result, #track-not-found | 71 ms |
| +2.87s | inner_text #track-status | 20 ms |
| +2.89s | goto http://127.0.0.1:8000/demo/freight/track/ | 56 ms |
| +2.90s | ⏱ track an unknown number | 414 ms |
| +2.95s | fill #track-id | 37 ms |
| +2.99s | click #track-btn | 272 ms |
| +3.26s | wait_for_selector #track-result, #track-not-found | 49 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-185037-r36/ |
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.32s] starting DEMO-018 [timing] goto http://127.0.0.1:8000/demo/freight/: 365ms [timing] open the home page: 365ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 65ms [timing] fill #track-id: 111ms [timing] click #track-btn: 290ms [timing] wait_for_selector #track-result, #track-not-found: 93ms [timing] track a shipment in transit: 560ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 197ms [timing] fill #track-id: 55ms [timing] click #track-btn: 304ms [timing] wait_for_selector #track-result, #track-not-found: 71ms [timing] track a delivered shipment: 627ms [timing] inner_text #track-status: 20ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 56ms [timing] fill #track-id: 37ms [timing] click #track-btn: 272ms [timing] wait_for_selector #track-result, #track-not-found: 49ms [timing] track an unknown number: 414ms [test] [ 3.33s] 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.