queued 2026-09-25 07:00:10 · started 07:00:17 · finished 07:00:22 · duration 5s · target v3.0.0 · chromium · trigger: schedule · batch: schedule: Freight regression 07:00
Activity replay 6 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.70s | goto http://127.0.0.1:8000/demo/freight/login/ | 195 ms |
| +0.90s | fill #username | 90 ms |
| +0.98s | fill #password | 16 ms |
| +1.00s | click #login-btn | 111 ms |
| +1.11s | wait_for_selector #signed-in-user | 127 ms |
| +1.25s | goto http://127.0.0.1:8000/demo/freight/ops/import/ | 33 ms |
| +1.27s | set_input_files #manifest-file | 38 ms |
| +1.32s | click #upload-btn | 64 ms |
| +1.32s | ⏱ process the manifest | 3.48 s |
| +1.37s | wait_for_selector #job-result, #job-failed | 3.41 s |
| +4.79s | get_attribute #job | 12 ms |
| +4.80s | inner_text #import-ok | 22 ms |
| +4.82s | inner_text #import-errors | 12 ms |
| +4.95s | click #download-result | 62 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 | manifest-results.csv |
| manifest.csv | |
| Folder | results/DEMO-015/20260925-070017-r490/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-015 browser=chromium headed=False timeout=150s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.70s] starting DEMO-015 [timing] goto http://127.0.0.1:8000/demo/freight/login/: 195ms [timing] fill #username: 90ms [timing] fill #password: 16ms [timing] click #login-btn: 111ms [timing] wait_for_selector #signed-in-user: 127ms [test] [ 1.24s] signed in as tester [timing] goto http://127.0.0.1:8000/demo/freight/ops/import/: 33ms [timing] set_input_files #manifest-file: 38ms [timing] click #upload-btn: 64ms [timing] wait_for_selector #job-result, #job-failed: 3406ms [timing] get_attribute #job: 12ms [timing] process the manifest: 3482ms [timing] inner_text #import-ok: 22ms [timing] inner_text #import-errors: 12ms [test] [ 4.83s] 27 rows priced, 3 with problems [test] [ 4.92s] screenshot: 01-import-result.png [timing] click #download-result: 62ms [test] [ 5.02s] downloaded manifest-results-91e2ad6c83df.csv [test] [ 5.02s] 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.