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

Run #473 — DEMO-023

passed
📄 Download report

queued 2026-09-25 00:30:11 · started 00:30:15 · finished 00:30:25 · duration 9s · target v3.0.0 · chromium · trigger: group · batch: group: Python and TypeScript, side by side

Activity replay 5 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.90s goto http://127.0.0.1:8000/demo/freight/login/ 148 ms
+1.05s click #forgot-link 204 ms
+1.26s fill #forgot-login 44 ms
+1.29s click #forgot-btn 76 ms
+1.38s inner_text #forgot-ref 34 ms
+1.40s ⏱ wait for the email 6.45 s
+1.41s goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example 40 ms
+1.44s wait_for_selector #mail-list a.mail-subject:has-text('ref 3AB3F8') 6.41 s
+7.86s click #mail-list a.mail-subject:has-text('ref 3AB3F8') 111 ms
+7.96s wait_for_selector #mail-body a[href*='/login/reset/'] 75 ms
+8.14s click #mail-body a[href*='/login/reset/'] 80 ms
+8.14s ⏱ choose a new password 306 ms
+8.22s fill #new-password 46 ms
+8.27s fill #confirm-password 32 ms
+8.30s click #reset-btn 118 ms
+8.42s wait_for_selector #login-btn 29 ms
+8.45s fill #username 13 ms
+8.45s ⏱ sign in with the new password 271 ms
+8.46s fill #password 21 ms
+8.48s click #login-btn 117 ms
+8.60s wait_for_selector #signed-in-user 119 ms
+8.71s click #sign-out 55 ms
+8.77s wait_for_selector #login-btn 30 ms
+8.80s ⏱ follow the same link again 141 ms
+8.80s goto http://127.0.0.1:8000/demo/freight/mailbox/7/ 30 ms
+8.84s click #mail-body a[href*='/login/reset/'] 74 ms
+8.90s wait_for_selector #reset-invalid, #reset-form 36 ms
+9.04s inner_text #reset-invalid-why 4 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/20260925-003015-r473/

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.90s] starting DEMO-023
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 148ms
[timing] click #forgot-link: 204ms
[timing] fill #forgot-login: 44ms
[timing] click #forgot-btn: 76ms
[timing] inner_text #forgot-ref: 34ms
[test] [   1.41s] reset requested, reference 3AB3F8
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example: 40ms
[timing] wait_for_selector #mail-list a.mail-subject:has-text('ref 3AB3F8'): 6406ms
[timing] wait for the email: 6447ms
[timing] click #mail-list a.mail-subject:has-text('ref 3AB3F8'): 111ms
[timing] wait_for_selector #mail-body a[href*='/login/reset/']: 75ms
[test] [   8.14s] screenshot: 01-the_reset_email.png
[timing] click #mail-body a[href*='/login/reset/']: 80ms
[timing] fill #new-password: 46ms
[timing] fill #confirm-password: 32ms
[timing] click #reset-btn: 118ms
[timing] wait_for_selector #login-btn: 29ms
[timing] choose a new password: 306ms
[timing] fill #username: 13ms
[timing] fill #password: 21ms
[timing] click #login-btn: 117ms
[timing] wait_for_selector #signed-in-user: 119ms
[timing] sign in with the new password: 271ms
[test] [   8.72s] signed in with the new password
[timing] click #sign-out: 55ms
[timing] wait_for_selector #login-btn: 30ms
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/7/: 30ms
[timing] click #mail-body a[href*='/login/reset/']: 74ms
[timing] wait_for_selector #reset-invalid, #reset-form: 36ms
[timing] follow the same link again: 141ms
[test] [   9.03s] screenshot: 02-the_same_link_a_second_time.png
[timing] inner_text #reset-invalid-why: 5ms
[test] [   9.04s] It has already been used to change the password — each reset link works once.
[test] [   9.04s] 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.