queued 2026-09-25 00:30:11 · started 00:30:17 · finished 00:30:19 · duration 1s · target v3.0.0 · chromium · trigger: group · batch: group: Python and TypeScript, side by side
Activity replay 1 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.60s | goto http://127.0.0.1:8000/demo/freight/login/ | 132 ms |
| +0.73s | fill #username | 75 ms |
| +0.81s | fill #password | 11 ms |
| +0.81s | click #login-btn | 106 ms |
| +0.92s | wait_for_selector #signed-in-user | 129 ms |
| +1.05s | goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/ | 65 ms |
| +1.11s | ⏱ open the label (a new tab) | 185 ms |
| +1.12s | click #print-label | 76 ms |
| +1.35s | ⏱ scan the barcode | 10 ms |
| +1.36s | ⏱ download the PDF | 38 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/20260925-003017-r474/ |
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.60s] starting DEMO-024 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 132ms [timing] fill #username: 75ms [timing] fill #password: 11ms [timing] click #login-btn: 106ms [timing] wait_for_selector #signed-in-user: 129ms [test] [ 1.05s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/: 65ms [timing] click #print-label: 76ms [timing] open the label (a new tab): 185ms [test] [ 1.30s] the label opened in a new tab: http://127.0.0.1:8000/demo/freight/ops/shipments/AF-100001/label/ [timing] scan the barcode: 10ms [test] [ 1.36s] the barcode reads 'AF-100001' [timing] download the PDF: 38ms [test] [ 1.40s] the PDF (2774 bytes) carries the same barcode [test] [ 1.40s] 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.