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

Run #334 — DEMO-013

passed
📄 Download report

queued 2026-09-24 19:48:13 · started 19:48:13 · finished 19:48:18 · duration 3s · target v3.0.0 · chromium · trigger: cli-adopted · batch: 4 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.89s goto http://127.0.0.1:8000/demo/freight/login/ 120 ms
+1.02s fill #username 153 ms
+1.17s fill #password 35 ms
+1.20s click #login-btn 167 ms
+1.37s wait_for_selector #signed-in-user 190 ms
+1.55s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 85 ms
+1.56s ⏱ search shipments 430 ms
+1.64s fill #shipment-search 80 ms
+1.73s select_option #status-filter 82 ms
+1.81s click #apply-filters 108 ms
+1.92s wait_for_selector #result-count 74 ms
+2.01s inner_text #result-count 10 ms
+2.02s ⏱ sort by ETA 195 ms
+2.02s click #shipments-table th a[data-sort=eta] 114 ms
+2.13s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 81 ms
+2.21s click #shipments-table a:text-is('AF-100001') 103 ms
+2.21s ⏱ open AF-100001 157 ms
+2.32s wait_for_selector #ship-status 54 ms
+2.49s fill #note-text 34 ms
+2.49s ⏱ save a note 120 ms
+2.52s click #note-save 63 ms
+2.59s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 23 ms
+2.65s ⏱ mark delivered 132 ms
+2.65s click #deliver-btn 88 ms
+2.74s wait_for_selector #ship-status:text-is('Delivered') 44 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-194813-r334/

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.89s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 120ms
[timing] fill #username: 153ms
[timing] fill #password: 35ms
[timing] click #login-btn: 167ms
[timing] wait_for_selector #signed-in-user: 190ms
[test] [   1.56s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 85ms
[timing] fill #shipment-search: 80ms
[timing] select_option #status-filter: 82ms
[timing] click #apply-filters: 108ms
[timing] wait_for_selector #result-count: 73ms
[timing] search shipments: 430ms
[timing] inner_text #result-count: 10ms
[test] [   2.02s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 114ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 81ms
[timing] sort by ETA: 195ms
[timing] click #shipments-table a:text-is('AF-100001'): 103ms
[timing] wait_for_selector #ship-status: 54ms
[timing] open AF-100001: 157ms
[test] [   2.49s] screenshot: 01-shipment.png
[timing] fill #note-text: 34ms
[timing] click #note-save: 63ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 23ms
[timing] save a note: 120ms
[timing] click #deliver-btn: 88ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 44ms
[timing] mark delivered: 133ms
[test] [   2.91s] screenshot: 02-delivered.png
[test] [   2.92s] 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.