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

Run #13 — DEMO-013

passed
📄 Download report

queued 2026-09-24 18:48:19 · started 18:48:59 · finished 18:49:03 · duration 4s · target v1.0.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)

Activity replay 5 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.74s goto http://127.0.0.1:8000/demo/freight/login/ 105 ms
+0.85s fill #username 80 ms
+0.93s fill #password 14 ms
+0.95s click #login-btn 301 ms
+1.24s wait_for_selector #signed-in-user 207 ms
+1.45s ⏱ search shipments 616 ms
+1.46s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 215 ms
+1.67s fill #shipment-search 90 ms
+1.76s select_option #status-filter 50 ms
+1.81s click #apply-filters 213 ms
+2.02s wait_for_selector #result-count 47 ms
+2.08s inner_text #result-count 11 ms
+2.09s ⏱ sort by ETA 228 ms
+2.09s click #shipments-table th a[data-sort=eta] 178 ms
+2.27s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 49 ms
+2.32s click #shipments-table a:text-is('AF-100001') 144 ms
+2.32s ⏱ open AF-100001 197 ms
+2.47s wait_for_selector #ship-status 54 ms
+2.62s fill #note-text 17 ms
+2.63s ⏱ save a note 114 ms
+2.64s click #note-save 61 ms
+2.70s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 36 ms
+2.75s ⏱ mark delivered 180 ms
+2.75s click #deliver-btn 127 ms
+2.88s wait_for_selector #ship-status:text-is('Delivered') 54 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-184859-r13/

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.75s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 105ms
[timing] fill #username: 80ms
[timing] fill #password: 14ms
[timing] click #login-btn: 301ms
[timing] wait_for_selector #signed-in-user: 207ms
[test] [   1.45s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 215ms
[timing] fill #shipment-search: 90ms
[timing] select_option #status-filter: 50ms
[timing] click #apply-filters: 213ms
[timing] wait_for_selector #result-count: 47ms
[timing] search shipments: 616ms
[timing] inner_text #result-count: 11ms
[test] [   2.09s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 178ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 49ms
[timing] sort by ETA: 228ms
[timing] click #shipments-table a:text-is('AF-100001'): 144ms
[timing] wait_for_selector #ship-status: 53ms
[timing] open AF-100001: 197ms
[test] [   2.62s] screenshot: 01-shipment.png
[timing] fill #note-text: 17ms
[timing] click #note-save: 61ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 36ms
[timing] save a note: 114ms
[timing] click #deliver-btn: 127ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 54ms
[timing] mark delivered: 181ms
[test] [   3.01s] screenshot: 02-delivered.png
[test] [   3.02s] 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.