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

Run #368 — DEMO-013

passed
📄 Download report

queued 2026-09-24 22:05:21 · started 22:05:26 · finished 22:05:30 · duration 4s · target v3.0.0 · chromium · trigger: group · batch: group: Freight regression

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.86s goto http://127.0.0.1:8000/demo/freight/login/ 194 ms
+1.06s fill #username 84 ms
+1.14s fill #password 30 ms
+1.17s click #login-btn 132 ms
+1.30s wait_for_selector #signed-in-user 130 ms
+1.43s ⏱ search shipments 359 ms
+1.43s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 76 ms
+1.51s fill #shipment-search 51 ms
+1.56s select_option #status-filter 79 ms
+1.64s click #apply-filters 93 ms
+1.73s wait_for_selector #result-count 59 ms
+1.79s inner_text #result-count 6 ms
+1.80s click #shipments-table th a[data-sort=eta] 81 ms
+1.81s ⏱ sort by ETA 134 ms
+1.89s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 52 ms
+1.94s click #shipments-table a:text-is('AF-100001') 115 ms
+1.94s ⏱ open AF-100001 203 ms
+2.05s wait_for_selector #ship-status 88 ms
+2.27s ⏱ save a note 195 ms
+2.27s fill #note-text 44 ms
+2.31s click #note-save 96 ms
+2.41s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 54 ms
+2.48s click #deliver-btn 158 ms
+2.48s ⏱ mark delivered 245 ms
+2.64s wait_for_selector #ship-status:text-is('Delivered') 86 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-220526-r368/

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.86s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 194ms
[timing] fill #username: 84ms
[timing] fill #password: 30ms
[timing] click #login-btn: 132ms
[timing] wait_for_selector #signed-in-user: 130ms
[test] [   1.43s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 76ms
[timing] fill #shipment-search: 51ms
[timing] select_option #status-filter: 79ms
[timing] click #apply-filters: 93ms
[timing] wait_for_selector #result-count: 59ms
[timing] search shipments: 359ms
[timing] inner_text #result-count: 6ms
[test] [   1.80s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 81ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 52ms
[timing] sort by ETA: 133ms
[timing] click #shipments-table a:text-is('AF-100001'): 115ms
[timing] wait_for_selector #ship-status: 88ms
[timing] open AF-100001: 203ms
[test] [   2.27s] screenshot: 01-shipment.png
[timing] fill #note-text: 44ms
[timing] click #note-save: 96ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 54ms
[timing] save a note: 195ms
[timing] click #deliver-btn: 158ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 86ms
[timing] mark delivered: 245ms
[test] [   2.96s] screenshot: 02-delivered.png
[test] [   2.97s] 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.