queued 2026-09-24 22:10:14 · started 22:10:18 · finished 22:10:20 · duration 2s · target v3.0.0 · chromium · trigger: schedule · batch: schedule: Freight smoke 22:10
Activity replay 2 frames, captured only while the page was actually changing — idle waits are skipped automatically
+0.00s
Step timings follows the replay — click a step to see it there
| at | step | took |
|---|---|---|
| +0.67s | goto http://127.0.0.1:8000/demo/freight/login/ | 192 ms |
| +0.90s | fill #username | 64 ms |
| +0.96s | fill #password | 41 ms |
| +1.00s | click #login-btn | 189 ms |
| +1.19s | wait_for_selector #signed-in-user | 189 ms |
| +1.58s | click #sign-out | 108 ms |
| +1.70s | wait_for_selector #login-btn | 75 ms |
| +1.79s | goto http://127.0.0.1:8000/demo/freight/ops/ | 57 ms |
Times are when each step began, on the replay's clock. Add your own phases with
with ctx.timed("label"):.
Screenshots
Artifacts
| Run log | run.log |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Folder | results/DEMO-012/20260924-221018-r375/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-012 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.67s] starting DEMO-012 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 193ms [test] [ 0.89s] logging in [timing] fill #username: 64ms [timing] fill #password: 41ms [timing] click #login-btn: 189ms [timing] wait_for_selector #signed-in-user: 189ms [test] [ 1.49s] screenshot: 01-signed-in.png [test] [ 1.58s] checked that http://127.0.0.1:8000/demo/freight/ops/ requires a session [timing] click #sign-out: 108ms [timing] wait_for_selector #login-btn: 75ms [timing] goto http://127.0.0.1:8000/demo/freight/ops/: 57ms [test] [ 1.85s] 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
| Severity | Finding | What 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.