queued 2026-09-25 00:24:06 · started 00:24:08 · finished 00:24:10 · duration 1s · target v3.0.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)
Activity replay 1 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.71s | ⏱ open the page | 95 ms |
| +0.71s | goto http://127.0.0.1:8000/demo/ | 95 ms |
| +0.80s | ⏱ fill the form | 208 ms |
| +0.81s | fill #name | 164 ms |
| +0.97s | fill #email | 33 ms |
| +1.00s | select_option #priority | 11 ms |
| +1.01s | click #submit-btn | 86 ms |
| +1.02s | ⏱ submit and wait for the result | 144 ms |
| +1.10s | wait_for_selector #result | 58 ms |
| +1.15s | inner_text #result | 6 ms |
| +1.16s | ⏱ check the result | 6 ms |
Times are when each step began, on the replay's clock. Add your own phases with
with ctx.timed("label"):.
Screenshots
No screenshots (use ctx.screenshot("name") in the test).
Artifacts
| Run log | run.log |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Folder | results/DEMO-007/20260925-002408-r440/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-007 browser=chromium headed=False timeout=120s [harness] target: http://127.0.0.1:8000/demo/ [test] [ 0.71s] starting DEMO-007 [timing] goto http://127.0.0.1:8000/demo/: 95ms [timing] open the page: 95ms [timing] fill #name: 164ms [timing] fill #email: 33ms [timing] select_option #priority: 11ms [timing] fill the form: 208ms [timing] click #submit-btn: 86ms [timing] wait_for_selector #result: 58ms [timing] submit and wait for the result: 144ms [timing] inner_text #result: 6ms [timing] check the result: 7ms [test] [ 1.17s] 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.