queued 2026-09-24 20:40:35 · started 20:40:36 · finished 20:40:39 · duration 3s · target v1.1.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.76s | goto http://127.0.0.1:8000/demo/freight/login/ | 196 ms |
| +0.96s | fill #username | 120 ms |
| +1.07s | fill #password | 38 ms |
| +1.11s | click #login-btn | 320 ms |
| +1.43s | wait_for_selector #signed-in-user | 156 ms |
| +1.58s | goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/ | 86 ms |
| +1.68s | ⏱ open the label (a new tab) | 194 ms |
| +1.68s | click #print-label | 93 ms |
| +1.93s | ⏱ scan the barcode | 11 ms |
| +1.94s | ⏱ download the PDF | 36 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-204036-r340/ |
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.76s] starting DEMO-024 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 196ms [timing] fill #username: 120ms [timing] fill #password: 38ms [timing] click #login-btn: 320ms [timing] wait_for_selector #signed-in-user: 156ms [test] [ 1.59s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/: 86ms [timing] click #print-label: 93ms [timing] open the label (a new tab): 194ms [test] [ 1.87s] the label opened in a new tab: http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/label/ [timing] scan the barcode: 11ms [test] [ 1.94s] the barcode reads 'AF-100001' [timing] download the PDF: 36ms [test] [ 1.98s] the PDF (2774 bytes) carries the same barcode [test] [ 2.31s] 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.