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

Run #342 — DEMO-023

passed
📄 Download report

queued 2026-09-24 20:40:49 · started 20:40:50 · finished 20:41:01 · duration 11s · target v2.0.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)

Activity replay 8 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.69s goto http://127.0.0.1:8000/demo/freight/login/ 169 ms
+0.85s click #forgot-link 297 ms
+1.15s fill #forgot-login 119 ms
+1.27s click #forgot-btn 147 ms
+1.42s inner_text #forgot-ref 34 ms
+1.46s goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example 63 ms
+1.46s ⏱ wait for the email 6.55 s
+1.52s wait_for_selector #mail-list a.mail-subject:has-text('ref D86604') 6.49 s
+8.00s click #mail-list a.mail-subject:has-text('ref D86604') 87 ms
+8.10s wait_for_selector #mail-body a[href*='/login/reset/'] 84 ms
+8.31s ⏱ choose a new password 732 ms
+8.31s click #mail-body a[href*='/login/reset/'] 110 ms
+8.41s fill #new-password 56 ms
+8.47s fill #confirm-password 167 ms
+8.64s click #reset-btn 252 ms
+8.89s wait_for_selector #login-btn 146 ms
+9.04s ⏱ sign in with the new password 522 ms
+9.04s fill #username 20 ms
+9.06s fill #password 33 ms
+9.10s click #login-btn 262 ms
+9.35s wait_for_selector #signed-in-user 206 ms
+9.56s click #sign-out 108 ms
+9.67s wait_for_selector #login-btn 52 ms
+9.72s ⏱ follow the same link again 200 ms
+9.73s goto http://127.0.0.1:8000/demo/freight/mailbox/3/ 43 ms
+9.77s click #mail-body a[href*='/login/reset/'] 102 ms
+9.87s wait_for_selector #reset-invalid, #reset-form 55 ms
+10.05s inner_text #reset-invalid-why 6 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-204050-r342/

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.69s] starting DEMO-023
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 169ms
[timing] click #forgot-link: 297ms
[timing] fill #forgot-login: 119ms
[timing] click #forgot-btn: 147ms
[timing] inner_text #forgot-ref: 34ms
[test] [   1.45s] reset requested, reference D86604
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example: 63ms
[timing] wait_for_selector #mail-list a.mail-subject:has-text('ref D86604'): 6490ms
[timing] wait for the email: 6552ms
[timing] click #mail-list a.mail-subject:has-text('ref D86604'): 87ms
[timing] wait_for_selector #mail-body a[href*='/login/reset/']: 84ms
[test] [   8.31s] screenshot: 01-the_reset_email.png
[timing] click #mail-body a[href*='/login/reset/']: 110ms
[timing] fill #new-password: 56ms
[timing] fill #confirm-password: 167ms
[timing] click #reset-btn: 252ms
[timing] wait_for_selector #login-btn: 146ms
[timing] choose a new password: 732ms
[timing] fill #username: 19ms
[timing] fill #password: 33ms
[timing] click #login-btn: 262ms
[timing] wait_for_selector #signed-in-user: 206ms
[timing] sign in with the new password: 522ms
[test] [   9.56s] signed in with the new password
[timing] click #sign-out: 108ms
[timing] wait_for_selector #login-btn: 52ms
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/3/: 43ms
[timing] click #mail-body a[href*='/login/reset/']: 102ms
[timing] wait_for_selector #reset-invalid, #reset-form: 55ms
[timing] follow the same link again: 200ms
[test] [  10.05s] screenshot: 02-the_same_link_a_second_time.png
[timing] inner_text #reset-invalid-why: 6ms
[test] [  10.06s] It has already been used to change the password — each reset link works once.
[test] [  10.06s] 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.