queued 2026-09-24 22:10:14 · started 22:10:14 · finished 22:10:18 · duration 3s · target v3.0.0 · chromium · trigger: schedule · batch: schedule: Freight smoke 22:10
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.72s | goto http://127.0.0.1:8000/demo/freight/ | 239 ms |
| +0.96s | inner_text #hero-title | 115 ms |
| +1.07s | get_attribute meta[name="app-version"] | 37 ms |
| +1.43s | goto http://127.0.0.1:8000/demo/freight/track/ | 77 ms |
| +1.44s | ⏱ track a shipment in transit | 415 ms |
| +1.50s | fill #track-id | 85 ms |
| +1.59s | click #track-btn | 186 ms |
| +1.77s | wait_for_selector #track-result, #track-not-found | 68 ms |
| +1.85s | inner_text #track-status | 13 ms |
| +1.86s | inner_text #track-destination | 8 ms |
| +2.07s | goto http://127.0.0.1:8000/demo/freight/track/ | 58 ms |
| +2.08s | ⏱ track an unknown number | 325 ms |
| +2.14s | fill #track-id | 42 ms |
| +2.18s | click #track-btn | 152 ms |
| +2.33s | 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
Artifacts
| Run log | run.log |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Folder | results/DEMO-010/20260924-221014-r373/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-010 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.72s] starting DEMO-010 [timing] goto http://127.0.0.1:8000/demo/freight/: 239ms [timing] inner_text #hero-title: 115ms [timing] get_attribute meta[name="app-version"]: 37ms [test] [ 1.11s] Acme Freight says it is release 3.0.0 [test] [ 1.43s] screenshot: 01-home.png [timing] goto http://127.0.0.1:8000/demo/freight/track/: 77ms [timing] fill #track-id: 85ms [timing] click #track-btn: 186ms [timing] wait_for_selector #track-result, #track-not-found: 68ms [timing] track a shipment in transit: 415ms [timing] inner_text #track-status: 13ms [timing] inner_text #track-destination: 8ms [test] [ 2.08s] screenshot: 02-tracking.png [timing] goto http://127.0.0.1:8000/demo/freight/track/: 58ms [timing] fill #track-id: 42ms [timing] click #track-btn: 152ms [timing] wait_for_selector #track-result, #track-not-found: 74ms [timing] track an unknown number: 325ms [test] [ 2.41s] PASSED [harness] security: 0 high, 1 medium, 1 low [harness] saved trace.zip [harness] saved video.webm [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.