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

Run #379 — DEMO-016

passed
📄 Download report

queued 2026-09-24 23:07:41 · started 23:07:41 · finished 23:09:16 · duration 1m 34s · target v3.0.0 · chromium · trigger: manual · batch: DEMO-016

Activity replay 20 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.58s goto http://127.0.0.1:8000/demo/freight/login/ 115 ms
+0.69s fill #username 65 ms
+0.77s fill #password 11 ms
+0.78s click #login-btn 161 ms
+0.93s wait_for_selector #signed-in-user 127 ms
+1.06s goto http://127.0.0.1:8000/demo/freight/ops/reports/ 29 ms
+1.12s click #sign-out 49 ms
+1.17s wait_for_selector #login-btn 42 ms
+1.20s goto http://127.0.0.1:8000/demo/freight/login/ 26 ms
+1.23s fill #username 20 ms
+1.25s fill #password 15 ms
+1.27s click #login-btn 151 ms
+1.42s wait_for_selector #signed-in-user 34 ms
+1.46s goto http://127.0.0.1:8000/demo/freight/ops/reports/ 32 ms
+1.48s check input[name=detail][value=full] 48 ms
+1.53s click #generate-report 70 ms
+1.61s wait_for_selector #job-progress 64 ms
+1.76s wait_for_selector #job-result, #job-failed 1m 31s
+1.76s ⏱ monthly report (full) 1m 31s
+1:32.86 get_attribute #job 7 ms
+1:32.86 inner_text #report-shipments 6 ms
+1:32.87 inner_text #report-revenue 6 ms
+1:32.95 click #download-result 48 ms

Times are when each step began, on the replay's clock. Add your own phases with with ctx.timed("label"):.

Screenshots

01-report-started.png
01-report-started.png
02-report.png
02-report.png

Artifacts

Run logrun.log
Playwright trace trace.zip open with: playwright show-trace trace.zip
Result JSONresult.json
Saved by the test report.csv
Folderresults/DEMO-016/20260924-230741-r379/

Full log

Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).

[harness] test=DEMO-016 browser=chromium headed=False timeout=420s
[harness] target: http://127.0.0.1:8000/demo/
[test] [   0.58s] starting DEMO-016
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 115ms
[timing] fill #username: 65ms
[timing] fill #password: 11ms
[timing] click #login-btn: 161ms
[timing] wait_for_selector #signed-in-user: 127ms
[test] [   1.06s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/reports/: 29ms
[test] [   1.12s] dispatcher correctly refused; switching to a manager
[timing] click #sign-out: 49ms
[timing] wait_for_selector #login-btn: 42ms
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 26ms
[timing] fill #username: 20ms
[timing] fill #password: 15ms
[timing] click #login-btn: 151ms
[timing] wait_for_selector #signed-in-user: 34ms
[test] [   1.45s] signed in as manager
[timing] goto http://127.0.0.1:8000/demo/freight/ops/reports/: 32ms
[timing] check input[name=detail][value=full]: 48ms
[timing] click #generate-report: 70ms
[timing] wait_for_selector #job-progress: 64ms
[test] [   1.76s] screenshot: 01-report-started.png
[timing] wait_for_selector #job-result, #job-failed: 91098ms
[timing] get_attribute #job: 7ms
[timing] monthly report (full): 91106ms
[timing] inner_text #report-shipments: 6ms
[timing] inner_text #report-revenue: 6ms
[test] [  92.88s] 357 shipments, revenue $394,263.13
[test] [  92.95s] screenshot: 02-report.png
[timing] click #download-result: 48ms
[test] [  93.01s] downloaded report-2026-09.csv
[test] [  93.01s] 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.