queued 2026-09-24 20:41:19 · started 20:41:20 · finished 20:41:23 · duration 3s · target v3.0.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)
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.69s | goto http://127.0.0.1:8000/demo/freight/login/ | 166 ms |
| +0.86s | fill #username | 122 ms |
| +0.98s | fill #password | 68 ms |
| +1.04s | click #login-btn | 228 ms |
| +1.28s | wait_for_selector #signed-in-user | 222 ms |
| +1.49s | goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/ | 108 ms |
| +1.60s | click #print-label | 115 ms |
| +1.61s | ⏱ open the label (a new tab) | 223 ms |
| +1.88s | ⏱ scan the barcode | 13 ms |
| +1.89s | ⏱ download the PDF | 63 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 |
| Saved by the test | label-AF-100001.pdf |
| Folder | results/DEMO-024/20260924-204120-r349/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-024 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.69s] starting DEMO-024 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 166ms [timing] fill #username: 122ms [timing] fill #password: 68ms [timing] click #login-btn: 228ms [timing] wait_for_selector #signed-in-user: 221ms [test] [ 1.50s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/: 108ms [timing] click #print-label: 115ms [timing] open the label (a new tab): 223ms [test] [ 1.83s] the label opened in a new tab: http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/label/ [timing] scan the barcode: 13ms [test] [ 1.89s] the barcode reads 'AF-100001' [timing] download the PDF: 63ms [test] [ 1.95s] the PDF (2774 bytes) carries the same barcode [test] [ 2.28s] 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
| 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.