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

Run #488 — DEMO-013

passed
📄 Download report

queued 2026-09-25 07:00:10 · started 07:00:13 · finished 07:00:16 · duration 3s · target v3.0.0 · chromium · trigger: schedule · batch: schedule: Freight regression 07:00

Activity replay 3 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/ 137 ms
+1.00s fill #username 78 ms
+1.07s fill #password 35 ms
+1.11s click #login-btn 131 ms
+1.25s wait_for_selector #signed-in-user 164 ms
+1.41s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 80 ms
+1.41s ⏱ search shipments 296 ms
+1.49s fill #shipment-search 42 ms
+1.53s select_option #status-filter 20 ms
+1.55s click #apply-filters 119 ms
+1.68s wait_for_selector #result-count 35 ms
+1.71s inner_text #result-count 6 ms
+1.72s click #shipments-table th a[data-sort=eta] 80 ms
+1.72s ⏱ sort by ETA 119 ms
+1.80s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 38 ms
+1.83s ⏱ open AF-100001 155 ms
+1.84s click #shipments-table a:text-is('AF-100001') 101 ms
+1.94s wait_for_selector #ship-status 54 ms
+2.10s ⏱ save a note 117 ms
+2.10s fill #note-text 15 ms
+2.12s click #note-save 46 ms
+2.16s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 56 ms
+2.23s click #deliver-btn 85 ms
+2.24s ⏱ mark delivered 148 ms
+2.33s wait_for_selector #ship-status:text-is('Delivered') 64 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/20260925-070013-r488/

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/: 137ms
[timing] fill #username: 78ms
[timing] fill #password: 35ms
[timing] click #login-btn: 131ms
[timing] wait_for_selector #signed-in-user: 164ms
[test] [   1.41s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 81ms
[timing] fill #shipment-search: 42ms
[timing] select_option #status-filter: 20ms
[timing] click #apply-filters: 119ms
[timing] wait_for_selector #result-count: 35ms
[timing] search shipments: 296ms
[timing] inner_text #result-count: 6ms
[test] [   1.72s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 80ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 38ms
[timing] sort by ETA: 119ms
[timing] click #shipments-table a:text-is('AF-100001'): 101ms
[timing] wait_for_selector #ship-status: 54ms
[timing] open AF-100001: 155ms
[test] [   2.11s] screenshot: 01-shipment.png
[timing] fill #note-text: 15ms
[timing] click #note-save: 46ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 56ms
[timing] save a note: 117ms
[timing] click #deliver-btn: 85ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 64ms
[timing] mark delivered: 148ms
[test] [   2.49s] screenshot: 02-delivered.png
[test] [   2.50s] PASSED
[harness] security: 0 high, 1 medium, 1 low
[harness] saved trace.zip
[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.