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

Run #16 — DEMO-016

passed
📄 Download report

queued 2026-09-24 18:48:19 · started 18:48:20 · finished 18:50:17 · duration 1m 56s · target v1.0.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)

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.75s goto http://127.0.0.1:8000/demo/freight/login/ 183 ms
+0.93s fill #username 113 ms
+1.04s fill #password 12 ms
+1.05s click #login-btn 273 ms
+1.32s wait_for_selector #signed-in-user 158 ms
+1.48s goto http://127.0.0.1:8000/demo/freight/ops/reports/ 46 ms
+1.57s click #sign-out 83 ms
+1.64s wait_for_selector #login-btn 36 ms
+1.68s goto http://127.0.0.1:8000/demo/freight/login/ 26 ms
+1.71s fill #username 30 ms
+1.74s fill #password 14 ms
+1.75s click #login-btn 272 ms
+2.02s wait_for_selector #signed-in-user 96 ms
+2.12s goto http://127.0.0.1:8000/demo/freight/ops/reports/ 39 ms
+2.16s check input[name=detail][value=full] 43 ms
+2.21s click #generate-report 75 ms
+2.28s wait_for_selector #job-progress 79 ms
+2.43s ⏱ monthly report (full) 1m 53s
+2.44s wait_for_selector #job-result, #job-failed 1m 53s
+1:55.53 get_attribute #job 7 ms
+1:55.54 inner_text #report-shipments 6 ms
+1:55.54 inner_text #report-revenue 6 ms
+1:55.62 click #download-result 62 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-184820-r16/

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.74s] starting DEMO-016
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 183ms
[timing] fill #username: 113ms
[timing] fill #password: 12ms
[timing] click #login-btn: 273ms
[timing] wait_for_selector #signed-in-user: 158ms
[test] [   1.48s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/reports/: 46ms
[test] [   1.56s] dispatcher correctly refused; switching to a manager
[timing] click #sign-out: 83ms
[timing] wait_for_selector #login-btn: 36ms
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 26ms
[timing] fill #username: 30ms
[timing] fill #password: 14ms
[timing] click #login-btn: 272ms
[timing] wait_for_selector #signed-in-user: 96ms
[test] [   2.12s] signed in as manager
[timing] goto http://127.0.0.1:8000/demo/freight/ops/reports/: 39ms
[timing] check input[name=detail][value=full]: 43ms
[timing] click #generate-report: 75ms
[timing] wait_for_selector #job-progress: 79ms
[test] [   2.43s] screenshot: 01-report-started.png
[timing] wait_for_selector #job-result, #job-failed: 113105ms
[timing] get_attribute #job: 7ms
[timing] monthly report (full): 113112ms
[timing] inner_text #report-shipments: 6ms
[timing] inner_text #report-revenue: 6ms
[test] [ 115.55s] 357 shipments, revenue $394,263.13
[test] [ 115.62s] screenshot: 02-report.png
[timing] click #download-result: 61ms
[test] [ 115.70s] downloaded report-2026-09.csv
[test] [ 115.70s] 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.