queued 2026-09-25 00:25:35 · started 00:25:36 · finished 00:27:38 · duration 2m 02s · target v3.0.0 · chromium · trigger: cli-adopted · batch: 2 tests (terminal)
Activity replay 14 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/?timer=120 | 129 ms |
| +0.83s | click #timer-btn | 144 ms |
| +0.98s | wait_for_selector #timer-panel:not(.hidden) | 34 ms |
| +1.07s | ⏱ job wait | 2m 00s |
| +1.07s | wait_for_selector #timer-done:not(.hidden) | 2m 00s |
| +2:01.43 | inner_text #timer-done | 8 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-006/20260925-002536-r459/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-006 browser=chromium headed=False timeout=400s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.70s] starting DEMO-006 [timing] goto http://127.0.0.1:8000/demo/?timer=120: 129ms [test] [ 0.83s] phase 1: start the job (this part is worth watching) [timing] click #timer-btn: 144ms [timing] wait_for_selector #timer-panel:not(.hidden): 34ms [test] [ 1.07s] screenshot: 01-job-started.png [test] [ 1.07s] phase 2: waiting up to 120s for it to finish [timing] wait_for_selector #timer-done:not(.hidden): 120308ms [timing] job wait: 120308ms [test] [ 121.38s] phase 3: the job finished -- check the outcome [test] [ 121.43s] screenshot: 02-job-finished.png [timing] inner_text #timer-done: 8ms [test] [ 121.44s] PASSED [harness] security: 0 high, 2 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. |
| medium | Missing Content-Security-Policy Without it, an injected script can run with the page's full privileges. This is the single most effective header against XSS. |
Set the Content-Security-Policy response header on the application or its reverse proxy. |
| 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.