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

Run #376 — DEMO-013

passed
📄 Download report

queued 2026-09-24 22:10:14 · started 22:10:18 · finished 22:10:22 · duration 3s · target v3.0.0 · chromium · trigger: schedule · batch: schedule: Freight smoke 22:10

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.78s goto http://127.0.0.1:8000/demo/freight/login/ 179 ms
+0.96s fill #username 60 ms
+1.02s fill #password 30 ms
+1.04s click #login-btn 156 ms
+1.20s wait_for_selector #signed-in-user 156 ms
+1.36s ⏱ search shipments 450 ms
+1.36s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 85 ms
+1.45s fill #shipment-search 79 ms
+1.52s select_option #status-filter 79 ms
+1.61s click #apply-filters 152 ms
+1.75s wait_for_selector #result-count 55 ms
+1.82s inner_text #result-count 9 ms
+1.82s click #shipments-table th a[data-sort=eta] 96 ms
+1.82s ⏱ sort by ETA 145 ms
+1.92s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 48 ms
+1.97s click #shipments-table a:text-is('AF-100001') 101 ms
+1.97s ⏱ open AF-100001 167 ms
+2.08s wait_for_selector #ship-status 66 ms
+2.25s fill #note-text 29 ms
+2.26s ⏱ save a note 161 ms
+2.28s click #note-save 118 ms
+2.41s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 14 ms
+2.43s ⏱ mark delivered 134 ms
+2.43s click #deliver-btn 71 ms
+2.50s wait_for_selector #ship-status:text-is('Delivered') 63 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-221018-r376/

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.78s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 179ms
[timing] fill #username: 60ms
[timing] fill #password: 29ms
[timing] click #login-btn: 156ms
[timing] wait_for_selector #signed-in-user: 156ms
[test] [   1.36s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 85ms
[timing] fill #shipment-search: 79ms
[timing] select_option #status-filter: 79ms
[timing] click #apply-filters: 152ms
[timing] wait_for_selector #result-count: 55ms
[timing] search shipments: 450ms
[timing] inner_text #result-count: 9ms
[test] [   1.83s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 97ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 48ms
[timing] sort by ETA: 145ms
[timing] click #shipments-table a:text-is('AF-100001'): 101ms
[timing] wait_for_selector #ship-status: 65ms
[timing] open AF-100001: 167ms
[test] [   2.26s] screenshot: 01-shipment.png
[timing] fill #note-text: 29ms
[timing] click #note-save: 118ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 14ms
[timing] save a note: 161ms
[timing] click #deliver-btn: 71ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 63ms
[timing] mark delivered: 134ms
[test] [   2.67s] screenshot: 02-delivered.png
[test] [   2.68s] 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

SeverityFindingWhat 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.