🧪 Test Hub
testing: Demo target v3.0.0 · built-in demo site
← →

Run #354 — DEMO-013

passed
📄 Download report

queued 2026-09-24 22:04:21 · started 22:04:25 · finished 22:04:29 · duration 3s · target v2.1.0 · chromium · trigger: group · batch: group: Freight smoke

Activity replay 4 frames, captured only while the page was actually changing — idle waits are skipped automatically

activity frame
+0.00s

Step timings follows the replay — click a step to see it there

atsteptook
+0.74s goto http://127.0.0.1:8000/demo/freight/login/ 200 ms
+0.94s fill #username 121 ms
+1.06s fill #password 33 ms
+1.09s click #login-btn 153 ms
+1.24s wait_for_selector #signed-in-user 176 ms
+1.42s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 102 ms
+1.42s ⏱ search shipments 378 ms
+1.52s fill #shipment-search 58 ms
+1.57s select_option #status-filter 45 ms
+1.62s click #apply-filters 128 ms
+1.75s wait_for_selector #result-count 46 ms
+1.80s inner_text #result-count 8 ms
+1.81s click #shipments-table th a[data-sort=eta] 108 ms
+1.81s ⏱ sort by ETA 156 ms
+1.92s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 48 ms
+1.97s ⏱ open AF-100001 132 ms
+1.97s click #shipments-table a:text-is('AF-100001') 78 ms
+2.05s wait_for_selector #ship-status 53 ms
+2.23s fill #note-text 25 ms
+2.23s ⏱ save a note 152 ms
+2.25s click #note-save 98 ms
+2.35s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 30 ms
+2.39s ⏱ mark delivered 126 ms
+2.40s click #deliver-btn 73 ms
+2.47s wait_for_selector #ship-status:text-is('Delivered') 53 ms

Times are when each step began, on the replay's clock. Add your own phases with with ctx.timed("label"):.

Screenshots

01-shipment.png
01-shipment.png
02-delivered.png
02-delivered.png

Artifacts

Run logrun.log
Playwright trace trace.zip open with: playwright show-trace trace.zip
Result JSONresult.json
Folderresults/DEMO-013/20260924-220425-r354/

Full log

Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).

[harness] test=DEMO-013 browser=chromium headed=False timeout=120s
[harness] target: http://127.0.0.1:8000/demo/
[test] [   0.74s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 200ms
[timing] fill #username: 121ms
[timing] fill #password: 33ms
[timing] click #login-btn: 153ms
[timing] wait_for_selector #signed-in-user: 176ms
[test] [   1.42s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 102ms
[timing] fill #shipment-search: 58ms
[timing] select_option #status-filter: 45ms
[timing] click #apply-filters: 128ms
[timing] wait_for_selector #result-count: 45ms
[timing] search shipments: 378ms
[timing] inner_text #result-count: 8ms
[test] [   1.81s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 108ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 48ms
[timing] sort by ETA: 156ms
[timing] click #shipments-table a:text-is('AF-100001'): 78ms
[timing] wait_for_selector #ship-status: 53ms
[timing] open AF-100001: 132ms
[test] [   2.23s] screenshot: 01-shipment.png
[timing] fill #note-text: 25ms
[timing] click #note-save: 98ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 30ms
[timing] save a note: 152ms
[timing] click #deliver-btn: 73ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 53ms
[timing] mark delivered: 126ms
[test] [   2.64s] screenshot: 02-delivered.png
[test] [   2.65s] PASSED
[harness] security: 1 high, 3 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

SeverityFindingWhat to do
high The page requested resources from other hosts
Requests went to: analytics.acme-metrics.invalid (7). On an air-gapped network these cannot succeed -- so the page is either broken or waiting on a timeout -- and each one is a path by which data could leave the enclave.
Vendor the resource locally, or remove the reference. This is worth chasing even when the page still appears to work.
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.
medium Missing Content-Security-Policy
Without it, an injected script can run with the page's full privileges. This is the single most effective header against XSS.
Set the Content-Security-Policy response header on the application or its reverse proxy.
medium Missing X-Frame-Options (or CSP frame-ancestors)
Without it, another site can embed this page invisibly and trick a user into clicking things (clickjacking).
Set the X-Frame-Options (or CSP frame-ancestors) response header on the application or its reverse proxy.
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.