queued 2026-09-24 18:57:59 · started 18:58:09 · finished 18:58:36 · duration 27s · target v2.1.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)
Activity replay 14 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.72s | goto http://127.0.0.1:8000/demo/freight/login/ | 130 ms |
| +0.85s | fill #username | 51 ms |
| +0.90s | fill #password | 21 ms |
| +0.92s | click #login-btn | 142 ms |
| +1.07s | wait_for_selector #signed-in-user | 222 ms |
| +1.29s | goto http://127.0.0.1:8000/demo/freight/ops/optimizer/ | 79 ms |
| +1.37s | select_option #region | 93 ms |
| +1.46s | fill #stops | 20 ms |
| +1.48s | fill #trucks | 52 ms |
| +1.53s | click #start-optimizer | 76 ms |
| +1.61s | wait_for_selector #job-progress | 83 ms |
| +1.79s | wait_for_selector #job-result, #job-failed | 24.25 s |
| +1.79s | ⏱ route optimization | 24.27 s |
| +26.05s | get_attribute #job | 15 ms |
| +26.06s | get_attribute #plan-saving | 9 ms |
| +26.06s | inner_text #plan-best | 7 ms |
| +26.07s | inner_text #plan-trucks | 7 ms |
| +26.17s | click #download-result | 36 ms |
Times are when each step began, on the replay's clock. Add your own phases with
with ctx.timed("label"):.
Artifacts
| Run log | run.log |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Saved by the test | route-plan.csv |
| Folder | results/DEMO-014/20260924-185809-r303/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-014 browser=chromium headed=False timeout=240s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.72s] starting DEMO-014 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 130ms [timing] fill #username: 51ms [timing] fill #password: 21ms [timing] click #login-btn: 142ms [timing] wait_for_selector #signed-in-user: 222ms [test] [ 1.29s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/optimizer/: 79ms [timing] select_option #region: 93ms [timing] fill #stops: 20ms [timing] fill #trucks: 52ms [timing] click #start-optimizer: 76ms [timing] wait_for_selector #job-progress: 83ms [test] [ 1.79s] screenshot: 01-optimizer-running.png [timing] wait_for_selector #job-result, #job-failed: 24254ms [timing] get_attribute #job: 15ms [timing] route optimization: 24269ms [timing] get_attribute #plan-saving: 9ms [timing] inner_text #plan-best: 7ms [test] [ 26.07s] optimized plan: 5,733 km (66.7% shorter than naive) [timing] inner_text #plan-trucks: 7ms [test] [ 26.17s] screenshot: 02-route-plan.png [timing] click #download-result: 36ms [test] [ 26.25s] downloaded route-plan-c8feaecbd495.csv [test] [ 26.25s] PASSED [harness] security: 1 high, 3 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 |
|---|---|---|
| high | The page requested resources from other hosts Requests went to: analytics.acme-metrics.invalid (5). On an air-gapped network these cannot succeed -- so the page is either broken or waiting on a timeout -- and each one is a path by which data could leave the enclave. |
Vendor the resource locally, or remove the reference. This is worth chasing even when the page still appears to work. |
| 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. |
| medium | Missing Content-Security-Policy Without it, an injected script can run with the page's full privileges. This is the single most effective header against XSS. |
Set the Content-Security-Policy response header on the application or its reverse proxy. |
| medium | Missing X-Frame-Options (or CSP frame-ancestors) Without it, another site can embed this page invisibly and trick a user into clicking things (clickjacking). |
Set the X-Frame-Options (or CSP frame-ancestors) response header on the application or its reverse proxy. |
| 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.

