queued 2026-09-25 00:30:11 · started 00:30:11 · finished 00:30:13 · duration 2s · target v3.0.0 · chromium · trigger: group · batch: group: Python and TypeScript, side by side
Activity replay 3 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/quote/?restart=1 | 211 ms |
| +0.93s | ⏱ route | 231 ms |
| +1.17s | ⏱ cargo | 185 ms |
| +1.35s | ⏱ choose a service | 148 ms |
| +1.50s | ⏱ apply promo SPRING10 | 259 ms |
| +1.68s | wait_for_selector #price-discount | 81 ms |
| +1.76s | get_attribute #price-subtotal | 10 ms |
| +1.77s | get_attribute #price-discount | 10 ms |
| +1.78s | get_attribute #price-fuel | 9 ms |
| +1.78s | get_attribute #price-total | 15 ms |
| +1.92s | ⏱ book | 195 ms |
| +2.04s | wait_for_selector #booking-id | 65 ms |
| +2.10s | inner_text #booking-id | 5 ms |
| +2.11s | ⏱ track the new booking | 121 ms |
| +2.20s | wait_for_selector #track-result | 31 ms |
| +2.23s | inner_text #track-status | 5 ms |
| +2.23s | inner_text #track-result | 5 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/20260925-003011-r470/ |
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.72s] starting DEMO-011 [timing] goto http://127.0.0.1:8000/demo/freight/quote/?restart=1: 211ms [timing] route: 231ms [timing] cargo: 185ms [timing] choose a service: 148ms [timing] wait_for_selector #price-discount: 81ms [timing] apply promo SPRING10: 259ms [timing] get_attribute #price-subtotal: 10ms [timing] get_attribute #price-discount: 10ms [timing] get_attribute #price-fuel: 9ms [timing] get_attribute #price-total: 15ms [test] [ 1.80s] subtotal $117.62, discount $11.76, total $114.86 [test] [ 1.91s] screenshot: 01-priced.png [timing] wait_for_selector #booking-id: 65ms [timing] book: 195ms [timing] inner_text #booking-id: 5ms [test] [ 2.11s] booked AF-953815 [timing] wait_for_selector #track-result: 31ms [timing] track the new booking: 121ms [timing] inner_text #track-status: 5ms [timing] inner_text #track-result: 5ms [test] [ 2.24s] 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.