queued 2026-09-24 18:55:04 · started 18:55:04 · finished 18:55:08 · duration 3s · target v1.1.0 · chromium · trigger: load
Step timings every page action is timed automatically
| at | step | took |
|---|---|---|
| +1.56s | ⏱ open the home page | 312 ms |
| +1.56s | goto http://127.0.0.1:8000/demo/freight/ | 312 ms |
| +1.87s | ⏱ track a shipment in transit | 332 ms |
| +1.87s | goto http://127.0.0.1:8000/demo/freight/track/ | 56 ms |
| +1.93s | fill #track-id | 74 ms |
| +2.00s | click #track-btn | 138 ms |
| +2.14s | wait_for_selector #track-result, #track-not-found | 64 ms |
| +2.20s | goto http://127.0.0.1:8000/demo/freight/track/ | 52 ms |
| +2.20s | ⏱ track a delivered shipment | 320 ms |
| +2.26s | fill #track-id | 43 ms |
| +2.29s | click #track-btn | 166 ms |
| +2.46s | wait_for_selector #track-result, #track-not-found | 59 ms |
| +2.52s | inner_text #track-status | 20 ms |
| +2.54s | goto http://127.0.0.1:8000/demo/freight/track/ | 51 ms |
| +2.54s | ⏱ track an unknown number | 308 ms |
| +2.59s | fill #track-id | 51 ms |
| +2.65s | click #track-btn | 133 ms |
| +2.78s | wait_for_selector #track-result, #track-not-found | 74 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-185504-r245/ |
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.56s] starting DEMO-018 [timing] goto http://127.0.0.1:8000/demo/freight/: 312ms [timing] open the home page: 312ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 56ms [timing] fill #track-id: 74ms [timing] click #track-btn: 138ms [timing] wait_for_selector #track-result, #track-not-found: 64ms [timing] track a shipment in transit: 332ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 52ms [timing] fill #track-id: 43ms [timing] click #track-btn: 166ms [timing] wait_for_selector #track-result, #track-not-found: 59ms [timing] track a delivered shipment: 320ms [timing] inner_text #track-status: 20ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 51ms [timing] fill #track-id: 51ms [timing] click #track-btn: 133ms [timing] wait_for_selector #track-result, #track-not-found: 74ms [timing] track an unknown number: 308ms [test] [ 2.87s] 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.