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

Run #310 — DEMO-013

passed
📄 Download report

queued 2026-09-24 18:59:58 · started 19:00:31 · finished 19:00:35 · duration 3s · target v3.0.0 · chromium · trigger: cli-adopted · batch: 8 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.74s goto http://127.0.0.1:8000/demo/freight/login/ 115 ms
+0.86s fill #username 78 ms
+0.94s fill #password 11 ms
+0.95s click #login-btn 124 ms
+1.08s wait_for_selector #signed-in-user 184 ms
+1.26s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 112 ms
+1.26s ⏱ search shipments 459 ms
+1.37s fill #shipment-search 91 ms
+1.47s select_option #status-filter 65 ms
+1.53s click #apply-filters 142 ms
+1.67s wait_for_selector #result-count 48 ms
+1.73s inner_text #result-count 7 ms
+1.74s click #shipments-table th a[data-sort=eta] 80 ms
+1.74s ⏱ sort by ETA 119 ms
+1.82s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 39 ms
+1.86s ⏱ open AF-100001 134 ms
+1.86s click #shipments-table a:text-is('AF-100001') 81 ms
+1.94s wait_for_selector #ship-status 52 ms
+2.10s fill #note-text 30 ms
+2.10s ⏱ save a note 178 ms
+2.13s click #note-save 51 ms
+2.18s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 97 ms
+2.29s ⏱ mark delivered 198 ms
+2.30s click #deliver-btn 90 ms
+2.38s wait_for_selector #ship-status:text-is('Delivered') 107 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-190031-r310/

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.74s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 115ms
[timing] fill #username: 78ms
[timing] fill #password: 11ms
[timing] click #login-btn: 124ms
[timing] wait_for_selector #signed-in-user: 184ms
[test] [   1.26s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 113ms
[timing] fill #shipment-search: 91ms
[timing] select_option #status-filter: 65ms
[timing] click #apply-filters: 142ms
[timing] wait_for_selector #result-count: 48ms
[timing] search shipments: 459ms
[timing] inner_text #result-count: 7ms
[test] [   1.74s] 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]: 39ms
[timing] sort by ETA: 119ms
[timing] click #shipments-table a:text-is('AF-100001'): 81ms
[timing] wait_for_selector #ship-status: 52ms
[timing] open AF-100001: 134ms
[test] [   2.10s] screenshot: 01-shipment.png
[timing] fill #note-text: 30ms
[timing] click #note-save: 51ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 97ms
[timing] save a note: 178ms
[timing] click #deliver-btn: 90ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 107ms
[timing] mark delivered: 198ms
[test] [   2.63s] screenshot: 02-delivered.png
[test] [   2.64s] 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.