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

Run #326 — DEMO-020

failed
📄 Download report

queued 2026-09-24 19:46:19 · started 19:46:19 · finished 19:46:21 · duration 2s · target v2.1.0 · chromium · trigger: cli-adopted · batch: 3 tests (terminal)

What went wrong

AssertionError: the API broke its promises:
  - contract: field 'eta' is missing (the response has: booked_at, customer, delivered_at, destination, estimated_delivery, events, id, origin, pieces, price, service, status, status_label, weight_kg)
  - money: SPRING10 took $23.52 off a $117.62 subtotal -- 10% is $11.76
  - limits: the trial key allows 5 calls a minute, but 6 in a row answered [200, 200, 200, 200, 200, 200]
Technical details (full error)
AssertionError: the API broke its promises:
  - contract: field 'eta' is missing (the response has: booked_at, customer, delivered_at, destination, estimated_delivery, events, id, origin, pieces, price, service, status, status_label, weight_kg)
  - money: SPRING10 took $23.52 off a $117.62 subtotal -- 10% is $11.76
  - limits: the trial key allows 5 calls a minute, but 6 in a row answered [200, 200, 200, 200, 200, 200]
Traceback (most recent call last):
  File "/opt/pw-testhub/app/core/harness/run_test.py", line 737, in main
    module.run(TimedPage(page, ctx), ctx)
  File "/opt/pw-testhub/data/tests/DEMO-020__freight_api_contract.py", line 73, in run
    assert not problems, "the API broke its promises:\n  - " + "\n  - ".join(problems)
AssertionError: the API broke its promises:
  - contract: field 'eta' is missing (the response has: booked_at, customer, delivered_at, destination, estimated_delivery, events, id, origin, pieces, price, service, status, status_label, weight_kg)
  - money: SPRING10 took $23.52 off a $117.62 subtotal -- 10% is $11.76
  - limits: the trial key allows 5 calls a minute, but 6 in a row answered [200, 200, 200, 200, 200, 200]
the page at the moment of failure
the page at the moment it failed

Activity replay 1 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.92s ⏱ auth: no key 31 ms
+0.95s ⏱ GET a shipment 44 ms
+0.99s ⏱ POST a quote with SPRING10 26 ms
+1.03s ⏱ rate limit: 6 calls on the trial key 323 ms

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

Screenshots

state at failure
state at failure

Artifacts

Run logrun.log
Playwright trace trace.zip open with: playwright show-trace trace.zip
Result JSONresult.json
Folderresults/DEMO-020/20260924-194619-r326/

Full log

Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).

[harness] test=DEMO-020 browser=chromium headed=False timeout=120s
[harness] target: http://127.0.0.1:8000/demo/
[test] [   0.92s] starting DEMO-020
[timing] auth: no key: 31ms
[timing] GET a shipment: 43ms
[timing] POST a quote with SPRING10: 26ms
[timing] rate limit: 6 calls on the trial key: 323ms
[test] [   1.35s] 3 broken promise(s)
[test] [   1.35s] FAILED: the API broke its promises:
  - contract: field 'eta' is missing (the response has: booked_at, customer, delivered_at, destination, estimated_delivery, events, id, origin, pieces, price, service, status, status_label, weight_kg)
  - money: SPRING10 took $23.52 off a $117.62 subtotal -- 10% is $11.76
  - limits: the trial key allows 5 calls a minute, but 6 in a row answered [200, 200, 200, 200, 200, 200]
[harness] security: 0 high, 1 medium, 0 low
[harness] saved failure.png
[harness] saved trace.zip
[harness] result: failed

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.
info No document response was observed
The test never loaded a top-level page from the target, so its headers could not be checked.
Have the test call page.goto(ctx.base_url) at least once.
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.