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

Run #363 — DEMO-023

passed
📄 Download report

queued 2026-09-24 22:05:07 · started 22:05:07 · finished 22:05:19 · duration 11s · target v3.0.0 · chromium · trigger: group · batch: group: Freight extras

Activity replay 6 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.73s goto http://127.0.0.1:8000/demo/freight/login/ 232 ms
+0.97s click #forgot-link 194 ms
+1.16s fill #forgot-login 43 ms
+1.19s click #forgot-btn 86 ms
+1.28s inner_text #forgot-ref 35 ms
+1.32s ⏱ wait for the email 6.56 s
+1.32s goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example 36 ms
+1.35s wait_for_selector #mail-list a.mail-subject:has-text('ref E1FD24') 6.53 s
+7.88s click #mail-list a.mail-subject:has-text('ref E1FD24') 135 ms
+8.02s wait_for_selector #mail-body a[href*='/login/reset/'] 84 ms
+8.24s ⏱ choose a new password 513 ms
+8.24s click #mail-body a[href*='/login/reset/'] 101 ms
+8.34s fill #new-password 114 ms
+8.45s fill #confirm-password 16 ms
+8.46s click #reset-btn 189 ms
+8.66s wait_for_selector #login-btn 93 ms
+8.75s ⏱ sign in with the new password 614 ms
+8.75s fill #username 38 ms
+8.78s fill #password 58 ms
+8.85s click #login-btn 461 ms
+9.30s wait_for_selector #signed-in-user 56 ms
+9.36s click #sign-out 100 ms
+9.47s wait_for_selector #login-btn 54 ms
+9.51s ⏱ follow the same link again 228 ms
+9.52s goto http://127.0.0.1:8000/demo/freight/mailbox/1/ 42 ms
+9.55s click #mail-body a[href*='/login/reset/'] 105 ms
+9.66s wait_for_selector #reset-invalid, #reset-form 80 ms
+9.85s inner_text #reset-invalid-why 10 ms

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

Screenshots

01-the_reset_email.png
01-the_reset_email.png
02-the_same_link_a_second_time.png
02-the_same_link_a_second_time.png

Artifacts

Run logrun.log
Playwright trace trace.zip open with: playwright show-trace trace.zip
Result JSONresult.json
Folderresults/DEMO-023/20260924-220507-r363/

Full log

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

[harness] test=DEMO-023 browser=chromium headed=False timeout=180s
[harness] target: http://127.0.0.1:8000/demo/
[test] [   0.73s] starting DEMO-023
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 233ms
[timing] click #forgot-link: 194ms
[timing] fill #forgot-login: 43ms
[timing] click #forgot-btn: 86ms
[timing] inner_text #forgot-ref: 35ms
[test] [   1.32s] reset requested, reference E1FD24
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example: 36ms
[timing] wait_for_selector #mail-list a.mail-subject:has-text('ref E1FD24'): 6525ms
[timing] wait for the email: 6561ms
[timing] click #mail-list a.mail-subject:has-text('ref E1FD24'): 135ms
[timing] wait_for_selector #mail-body a[href*='/login/reset/']: 84ms
[test] [   8.23s] screenshot: 01-the_reset_email.png
[timing] click #mail-body a[href*='/login/reset/']: 101ms
[timing] fill #new-password: 114ms
[timing] fill #confirm-password: 16ms
[timing] click #reset-btn: 189ms
[timing] wait_for_selector #login-btn: 93ms
[timing] choose a new password: 513ms
[timing] fill #username: 38ms
[timing] fill #password: 58ms
[timing] click #login-btn: 461ms
[timing] wait_for_selector #signed-in-user: 56ms
[timing] sign in with the new password: 614ms
[test] [   9.36s] signed in with the new password
[timing] click #sign-out: 100ms
[timing] wait_for_selector #login-btn: 54ms
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/1/: 42ms
[timing] click #mail-body a[href*='/login/reset/']: 105ms
[timing] wait_for_selector #reset-invalid, #reset-form: 80ms
[timing] follow the same link again: 228ms
[test] [   9.84s] screenshot: 02-the_same_link_a_second_time.png
[timing] inner_text #reset-invalid-why: 10ms
[test] [   9.86s] It has already been used to change the password — each reset link works once.
[test] [   9.86s] 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.