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

Run #295 — DEMO-013

passed
📄 Download report

queued 2026-09-24 18:57:39 · started 18:57:40 · finished 18:57:43 · duration 3s · target v2.0.0 · chromium · trigger: cli-adopted · batch: DEMO-013

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.59s goto http://127.0.0.1:8000/demo/freight/login/ 108 ms
+0.70s fill #username 78 ms
+0.78s fill #password 20 ms
+0.80s click #login-btn 120 ms
+0.92s wait_for_selector #signed-in-user 152 ms
+1.07s goto http://127.0.0.1:8000/demo/freight/ops/shipments/ 84 ms
+1.07s ⏱ search shipments 347 ms
+1.15s fill #shipment-search 61 ms
+1.22s select_option #status-filter 45 ms
+1.26s click #apply-filters 111 ms
+1.38s wait_for_selector #result-count 45 ms
+1.42s inner_text #result-count 6 ms
+1.43s click #shipments-table th a[data-sort=eta] 95 ms
+1.43s ⏱ sort by ETA 144 ms
+1.52s wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] 48 ms
+1.57s ⏱ open AF-100001 180 ms
+1.57s click #shipments-table a:text-is('AF-100001') 108 ms
+1.68s wait_for_selector #ship-status 72 ms
+1.87s ⏱ save a note 153 ms
+1.87s fill #note-text 16 ms
+1.89s click #note-save 104 ms
+1.99s wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) 32 ms
+2.03s ⏱ mark delivered 130 ms
+2.03s click #deliver-btn 79 ms
+2.11s wait_for_selector #ship-status:text-is('Delivered') 50 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-185740-r295/

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.59s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 108ms
[timing] fill #username: 78ms
[timing] fill #password: 20ms
[timing] click #login-btn: 120ms
[timing] wait_for_selector #signed-in-user: 152ms
[test] [   1.07s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 84ms
[timing] fill #shipment-search: 61ms
[timing] select_option #status-filter: 45ms
[timing] click #apply-filters: 111ms
[timing] wait_for_selector #result-count: 45ms
[timing] search shipments: 347ms
[timing] inner_text #result-count: 6ms
[test] [   1.43s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 95ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 48ms
[timing] sort by ETA: 144ms
[timing] click #shipments-table a:text-is('AF-100001'): 108ms
[timing] wait_for_selector #ship-status: 72ms
[timing] open AF-100001: 180ms
[test] [   1.87s] screenshot: 01-shipment.png
[timing] fill #note-text: 16ms
[timing] click #note-save: 104ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 32ms
[timing] save a note: 153ms
[timing] click #deliver-btn: 79ms
[timing] wait_for_selector #ship-status:text-is('Delivered'): 50ms
[timing] mark delivered: 130ms
[test] [   2.30s] screenshot: 02-delivered.png
[test] [   2.31s] 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.