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

Run #302 — DEMO-013

passed
📄 Download report

queued 2026-09-24 18:57:59 · started 18:58:37 · finished 18:58:41 · duration 3s · target v2.1.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)

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.64s goto http://127.0.0.1:8000/demo/freight/login/ 215 ms
+0.84s fill #username 78 ms
+0.92s fill #password 60 ms
+0.98s click #login-btn 187 ms
+1.17s wait_for_selector #signed-in-user 132 ms
+1.30s ⏱ search shipments 368 ms
+1.30s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 88 ms
+1.39s fill #shipment-search 48 ms
+1.44s select_option #status-filter 61 ms
+1.50s click #apply-filters 121 ms
+1.62s wait_for_selector #result-count 50 ms
+1.68s inner_text #result-count 10 ms
+1.69s ⏱ sort by ETA 227 ms
+1.69s click #shipments-table th a[data-sort=eta] 146 ms
+1.84s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 81 ms
+1.92s click #shipments-table a:text-is('AF-100001') 142 ms
+1.92s ⏱ open AF-100001 240 ms
+2.06s wait_for_selector #ship-status 97 ms
+2.27s ⏱ save a note 147 ms
+2.28s fill #note-text 23 ms
+2.29s click #note-save 75 ms
+2.37s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 50 ms
+2.43s click #deliver-btn 70 ms
+2.43s ⏱ mark delivered 126 ms
+2.50s wait_for_selector #ship-status:text-is('Delivered') 55 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-185837-r302/

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.63s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 215ms
[timing] fill #username: 77ms
[timing] fill #password: 60ms
[timing] click #login-btn: 187ms
[timing] wait_for_selector #signed-in-user: 132ms
[test] [   1.30s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 88ms
[timing] fill #shipment-search: 48ms
[timing] select_option #status-filter: 61ms
[timing] click #apply-filters: 121ms
[timing] wait_for_selector #result-count: 50ms
[timing] search shipments: 368ms
[timing] inner_text #result-count: 10ms
[test] [   1.69s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 146ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 81ms
[timing] sort by ETA: 227ms
[timing] click #shipments-table a:text-is('AF-100001'): 142ms
[timing] wait_for_selector #ship-status: 97ms
[timing] open AF-100001: 240ms
[test] [   2.28s] screenshot: 01-shipment.png
[timing] fill #note-text: 23ms
[timing] click #note-save: 75ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 50ms
[timing] save a note: 147ms
[timing] click #deliver-btn: 70ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 55ms
[timing] mark delivered: 126ms
[test] [   2.68s] screenshot: 02-delivered.png
[test] [   2.69s] 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.