🧪 Test Hub
testing: Demo target v3.0.0 · built-in demo site
← →

Run #381 — DEMO-011

passed
📄 Download report

queued 2026-09-24 23:10:27 · started 23:10:27 · finished 23:10:30 · duration 2s · target v3.0.0 · chromium · trigger: group · batch: group: Freight smoke

Activity replay 3 frames, captured only while the page was actually changing — idle waits are skipped automatically

activity frame
+0.00s

Step timings follows the replay — click a step to see it there

atsteptook
+0.72s goto http://127.0.0.1:8000/demo/freight/quote/?restart=1 182 ms
+0.90s ⏱ route 288 ms
+1.19s ⏱ cargo 222 ms
+1.41s ⏱ choose a service 171 ms
+1.59s ⏱ apply promo SPRING10 244 ms
+1.75s wait_for_selector #price-discount 75 ms
+1.83s get_attribute #price-subtotal 13 ms
+1.84s get_attribute #price-discount 10 ms
+1.85s get_attribute #price-fuel 10 ms
+1.86s get_attribute #price-total 10 ms
+1.99s ⏱ book 217 ms
+2.15s wait_for_selector #booking-id 58 ms
+2.21s inner_text #booking-id 7 ms
+2.22s ⏱ track the new booking 127 ms
+2.31s wait_for_selector #track-result 37 ms
+2.35s inner_text #track-status 7 ms
+2.36s inner_text #track-result 4 ms

Times are when each step began, on the replay's clock. Add your own phases with with ctx.timed("label"):.

Screenshots

01-priced.png
01-priced.png

Artifacts

Run logrun.log
Playwright trace trace.zip open with: playwright show-trace trace.zip
Result JSONresult.json
Folderresults/DEMO-011/20260924-231027-r381/

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: 182ms
[timing] route: 288ms
[timing] cargo: 223ms
[timing] choose a service: 171ms
[timing] wait_for_selector #price-discount: 75ms
[timing] apply promo SPRING10: 244ms
[timing] get_attribute #price-subtotal: 13ms
[timing] get_attribute #price-discount: 10ms
[timing] get_attribute #price-fuel: 10ms
[timing] get_attribute #price-total: 10ms
[test] [   1.87s] subtotal $117.62, discount $11.76, total $114.86
[test] [   2.00s] screenshot: 01-priced.png
[timing] wait_for_selector #booking-id: 58ms
[timing] book: 217ms
[timing] inner_text #booking-id: 7ms
[test] [   2.22s] booked AF-935458
[timing] wait_for_selector #track-result: 37ms
[timing] track the new booking: 127ms
[timing] inner_text #track-status: 7ms
[timing] inner_text #track-result: 4ms
[test] [   2.36s] 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

SeverityFindingWhat 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.