queued 2026-09-24 18:50:19 · started 18:50:21 · finished 18:50:23 · duration 2s · target v1.0.0 · chromium · trigger: cli-adopted · batch: DEMO-018
Activity replay 3 frames, captured only while the page was actually changing — idle waits are skipped automatically
+0.00s
Step timings follows the replay — click a step to see it there
| at | step | took |
|---|---|---|
| +0.60s | ⏱ open the home page | 163 ms |
| +0.60s | goto http://127.0.0.1:8000/demo/freight/ | 163 ms |
| +0.76s | ⏱ track a shipment in transit | 392 ms |
| +0.76s | goto http://127.0.0.1:8000/demo/freight/track/ | 42 ms |
| +0.80s | fill #track-id | 42 ms |
| +0.84s | click #track-btn | 248 ms |
| +1.09s | wait_for_selector #track-result, #track-not-found | 60 ms |
| +1.15s | goto http://127.0.0.1:8000/demo/freight/track/ | 24 ms |
| +1.15s | ⏱ track a delivered shipment | 337 ms |
| +1.17s | fill #track-id | 26 ms |
| +1.20s | click #track-btn | 238 ms |
| +1.44s | wait_for_selector #track-result, #track-not-found | 48 ms |
| +1.48s | inner_text #track-status | 7 ms |
| +1.50s | goto http://127.0.0.1:8000/demo/freight/track/ | 24 ms |
| +1.50s | ⏱ track an unknown number | 333 ms |
| +1.51s | fill #track-id | 25 ms |
| +1.54s | click #track-btn | 245 ms |
| +1.79s | wait_for_selector #track-result, #track-not-found | 39 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 |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Folder | results/DEMO-018/20260924-185021-r18/ |
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] [ 0.59s] starting DEMO-018 [timing] goto http://127.0.0.1:8000/demo/freight/: 163ms [timing] open the home page: 163ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 42ms [timing] fill #track-id: 42ms [timing] click #track-btn: 248ms [timing] wait_for_selector #track-result, #track-not-found: 60ms [timing] track a shipment in transit: 392ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 24ms [timing] fill #track-id: 26ms [timing] click #track-btn: 238ms [timing] wait_for_selector #track-result, #track-not-found: 48ms [timing] track a delivered shipment: 337ms [timing] inner_text #track-status: 7ms [timing] goto http://127.0.0.1:8000/demo/freight/track/: 24ms [timing] fill #track-id: 25ms [timing] click #track-btn: 245ms [timing] wait_for_selector #track-result, #track-not-found: 39ms [timing] track an unknown number: 333ms [test] [ 1.83s] PASSED [harness] security: 0 high, 1 medium, 1 low [harness] saved trace.zip [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.