queued 2026-09-24 18:48:19 · started 18:49:07 · finished 18:49:10 · duration 3s · target v1.0.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)
Activity replay 4 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.67s | goto http://127.0.0.1:8000/demo/freight/quote/?restart=1 | 138 ms |
| +0.81s | ⏱ route | 261 ms |
| +1.07s | ⏱ cargo | 343 ms |
| +1.41s | ⏱ choose a service | 98 ms |
| +1.51s | ⏱ apply promo SPRING10 | 198 ms |
| +1.64s | wait_for_selector #price-discount | 66 ms |
| +1.71s | get_attribute #price-subtotal | 7 ms |
| +1.72s | get_attribute #price-discount | 5 ms |
| +1.72s | get_attribute #price-total | 6 ms |
| +1.73s | get_attribute #price-fuel | 5 ms |
| +1.80s | ⏱ book | 227 ms |
| +1.95s | wait_for_selector #booking-id | 81 ms |
| +2.02s | inner_text #booking-id | 8 ms |
| +2.03s | ⏱ track the new booking | 309 ms |
| +2.27s | wait_for_selector #track-result | 69 ms |
| +2.34s | inner_text #track-status | 17 ms |
| +2.36s | inner_text #track-result | 10 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 |
| Folder | results/DEMO-011/20260924-184907-r11/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-011 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.67s] starting DEMO-011 [timing] goto http://127.0.0.1:8000/demo/freight/quote/?restart=1: 138ms [timing] route: 261ms [timing] cargo: 343ms [timing] choose a service: 98ms [timing] wait_for_selector #price-discount: 66ms [timing] apply promo SPRING10: 198ms [timing] get_attribute #price-subtotal: 7ms [timing] get_attribute #price-discount: 5ms [timing] get_attribute #price-fuel: 5ms [timing] get_attribute #price-total: 5ms [test] [ 1.73s] subtotal $117.62, discount $11.76, total $114.86 [test] [ 1.80s] screenshot: 01-priced.png [timing] wait_for_selector #booking-id: 81ms [timing] book: 227ms [timing] inner_text #booking-id: 8ms [test] [ 2.03s] booked AF-906536 [timing] wait_for_selector #track-result: 69ms [timing] track the new booking: 309ms [timing] inner_text #track-status: 17ms [timing] inner_text #track-result: 10ms [test] [ 2.37s] 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.