queued 2026-09-25 07:00:10 · started 07:00:15 · finished 07:00:35 · duration 19s · target v3.0.0 · chromium · trigger: schedule · batch: schedule: Freight regression 07:00
Activity replay 15 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.81s | goto http://127.0.0.1:8000/demo/freight/login/ | 126 ms |
| +0.94s | fill #username | 62 ms |
| +1.00s | fill #password | 12 ms |
| +1.01s | click #login-btn | 119 ms |
| +1.13s | wait_for_selector #signed-in-user | 136 ms |
| +1.26s | goto http://127.0.0.1:8000/demo/freight/ops/optimizer/ | 36 ms |
| +1.30s | select_option #region | 28 ms |
| +1.33s | fill #stops | 12 ms |
| +1.34s | fill #trucks | 26 ms |
| +1.37s | click #start-optimizer | 81 ms |
| +1.45s | wait_for_selector #job-progress | 92 ms |
| +1.64s | ⏱ route optimization | 17.14 s |
| +1.64s | wait_for_selector #job-result, #job-failed | 17.13 s |
| +18.77s | get_attribute #job | 13 ms |
| +18.79s | get_attribute #plan-saving | 14 ms |
| +18.80s | inner_text #plan-best | 10 ms |
| +18.80s | inner_text #plan-trucks | 5 ms |
| +18.89s | click #download-result | 43 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 | route-plan.csv |
| Folder | results/DEMO-014/20260925-070015-r489/ |
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.81s] starting DEMO-014 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 126ms [timing] fill #username: 62ms [timing] fill #password: 12ms [timing] click #login-btn: 119ms [timing] wait_for_selector #signed-in-user: 136ms [test] [ 1.27s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/optimizer/: 36ms [timing] select_option #region: 28ms [timing] fill #stops: 12ms [timing] fill #trucks: 26ms [timing] click #start-optimizer: 81ms [timing] wait_for_selector #job-progress: 92ms [test] [ 1.64s] screenshot: 01-optimizer-running.png [timing] wait_for_selector #job-result, #job-failed: 17130ms [timing] get_attribute #job: 13ms [timing] route optimization: 17143ms [timing] get_attribute #plan-saving: 14ms [timing] inner_text #plan-best: 10ms [test] [ 18.81s] optimized plan: 5,733 km (66.7% shorter than naive) [timing] inner_text #plan-trucks: 5ms [test] [ 18.88s] screenshot: 02-route-plan.png [timing] click #download-result: 43ms [test] [ 18.94s] downloaded route-plan-7af0d05ad8d1.csv [test] [ 18.94s] 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.