queued 2026-09-24 18:52:00 · started 18:52:49 · finished 18:52:51 · duration 2s · target v1.1.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)
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.61s | goto http://127.0.0.1:8000/demo/freight/ | 275 ms |
| +0.89s | inner_text #hero-title | 96 ms |
| +0.99s | get_attribute meta[name="app-version"] | 31 ms |
| +1.18s | goto http://127.0.0.1:8000/demo/freight/track/ | 54 ms |
| +1.18s | ⏱ track a shipment in transit | 281 ms |
| +1.23s | fill #track-id | 40 ms |
| +1.28s | click #track-btn | 123 ms |
| +1.40s | wait_for_selector #track-result, #track-not-found | 63 ms |
| +1.45s | inner_text #track-status | 6 ms |
| +1.47s | inner_text #track-destination | 5 ms |
| +1.55s | goto http://127.0.0.1:8000/demo/freight/track/ | 46 ms |
| +1.56s | ⏱ track an unknown number | 251 ms |
| +1.61s | fill #track-id | 43 ms |
| +1.64s | click #track-btn | 117 ms |
| +1.76s | wait_for_selector #track-result, #track-not-found | 45 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-185249-r148/ |
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.62s] starting DEMO-010 [timing] goto http://127.0.0.1:8000/demo/freight/: 275ms [timing] inner_text #hero-title: 96ms [timing] get_attribute meta[name="app-version"]: 31ms [test] [ 1.02s] Acme Freight says it is release 1.1.0 [test] [ 1.18s] screenshot: 01-home.png [timing] goto http://127.0.0.1:8000/demo/freight/track/: 54ms [timing] fill #track-id: 40ms [timing] click #track-btn: 123ms [timing] wait_for_selector #track-result, #track-not-found: 63ms [timing] track a shipment in transit: 281ms [timing] inner_text #track-status: 6ms [timing] inner_text #track-destination: 5ms [test] [ 1.56s] screenshot: 02-tracking.png [timing] goto http://127.0.0.1:8000/demo/freight/track/: 46ms [timing] fill #track-id: 43ms [timing] click #track-btn: 117ms [timing] wait_for_selector #track-result, #track-not-found: 45ms [timing] track an unknown number: 251ms [test] [ 1.82s] 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.