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

Run #339 — DEMO-023

passed
📄 Download report

queued 2026-09-24 20:40:35 · started 20:40:36 · finished 20:40:47 · duration 11s · target v1.1.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)

Activity replay 7 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.76s goto http://127.0.0.1:8000/demo/freight/login/ 183 ms
+0.95s click #forgot-link 254 ms
+1.20s fill #forgot-login 83 ms
+1.28s click #forgot-btn 121 ms
+1.40s inner_text #forgot-ref 47 ms
+1.45s ⏱ wait for the email 6.55 s
+1.45s goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example 97 ms
+1.55s wait_for_selector #mail-list a.mail-subject:has-text('ref 1A5F39') 6.45 s
+8.00s click #mail-list a.mail-subject:has-text('ref 1A5F39') 82 ms
+8.09s wait_for_selector #mail-body a[href*='/login/reset/'] 64 ms
+8.25s ⏱ choose a new password 474 ms
+8.25s click #mail-body a[href*='/login/reset/'] 91 ms
+8.35s fill #new-password 115 ms
+8.46s fill #confirm-password 51 ms
+8.51s click #reset-btn 135 ms
+8.64s wait_for_selector #login-btn 82 ms
+8.72s ⏱ sign in with the new password 508 ms
+8.72s fill #username 25 ms
+8.75s fill #password 44 ms
+8.79s click #login-btn 378 ms
+9.17s wait_for_selector #signed-in-user 61 ms
+9.23s click #sign-out 122 ms
+9.35s wait_for_selector #login-btn 57 ms
+9.41s goto http://127.0.0.1:8000/demo/freight/mailbox/2/ 59 ms
+9.41s ⏱ follow the same link again 205 ms
+9.47s click #mail-body a[href*='/login/reset/'] 101 ms
+9.57s wait_for_selector #reset-invalid, #reset-form 45 ms
+9.70s inner_text #reset-invalid-why 14 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-204036-r339/

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.76s] starting DEMO-023
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 183ms
[timing] click #forgot-link: 254ms
[timing] fill #forgot-login: 83ms
[timing] click #forgot-btn: 121ms
[timing] inner_text #forgot-ref: 47ms
[test] [   1.45s] reset requested, reference 1A5F39
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/?to=driver@acme-freight.example: 97ms
[timing] wait_for_selector #mail-list a.mail-subject:has-text('ref 1A5F39'): 6452ms
[timing] wait for the email: 6550ms
[timing] click #mail-list a.mail-subject:has-text('ref 1A5F39'): 82ms
[timing] wait_for_selector #mail-body a[href*='/login/reset/']: 64ms
[test] [   8.25s] screenshot: 01-the_reset_email.png
[timing] click #mail-body a[href*='/login/reset/']: 91ms
[timing] fill #new-password: 115ms
[timing] fill #confirm-password: 51ms
[timing] click #reset-btn: 135ms
[timing] wait_for_selector #login-btn: 82ms
[timing] choose a new password: 474ms
[timing] fill #username: 25ms
[timing] fill #password: 44ms
[timing] click #login-btn: 378ms
[timing] wait_for_selector #signed-in-user: 61ms
[timing] sign in with the new password: 508ms
[test] [   9.23s] signed in with the new password
[timing] click #sign-out: 121ms
[timing] wait_for_selector #login-btn: 57ms
[timing] goto http://127.0.0.1:8000/demo/freight/mailbox/2/: 59ms
[timing] click #mail-body a[href*='/login/reset/']: 101ms
[timing] wait_for_selector #reset-invalid, #reset-form: 45ms
[timing] follow the same link again: 205ms
[test] [   9.68s] screenshot: 02-the_same_link_a_second_time.png
[timing] inner_text #reset-invalid-why: 14ms
[test] [   9.71s] It has already been used to change the password — each reset link works once.
[test] [   9.71s] 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.