Green on my machine, red on the runner — it was replaying a HAR the whole time

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

Spent most of a day on this so I am writing it down.

A colleague recorded @har:posts a fortnight ago. Since then my local runs have been passing against a payload that no longer exists on staging, because the recording was sitting in the project and I never passed a HAR flag in my life. CI has a clean checkout, so it saw the same file and passed too — until the endpoint changed shape and the assertion started failing on the one job that runs against the live API.

bash

bun run sdods run -p demo-shop -e staging -l api -t @smoke

How do I run the plain command and get the real network? I tried SDODS_HAR_MODE=off and it still replayed.

har ci api

asked by Yusuf Demir

2 answers

Accepted answer
Because off does not mean off once a file exists. The mode resolution is: take the requested mode, and if it is anything other than off use it; if it is off, fall through to a file check and replay when the recording is there. SDODS_HAR_MODE=off lands you in exactly that fall-through, which is why it changed nothing.
Two ways to get the live network for a @har-tagged scenario:
1. sdods run ... --har-update, which hits the real service and rewrites the file as it goes.
2. Move the recording out of har/<env>/ for the duration.
If what you actually want is a job that proves the live API still matches, drop the @har tag from that scenario and use a recorded copy of it for the offline job instead. A scenario that is tagged for replay is not a contract test, and it will never fail when the service changes.
answered by Jide Okonkwo
Fair complaint about the surface, and I will own it: the mode table documents off as "no HAR routing", and the resolution then treats off as "decide from the filesystem". Those two sentences do not say the same thing, and you are the second person to lose a day to the gap.
Until that is reconciled, the reliable statement is the one to put in your team notes: once har/<env>/<name>.har exists, that scenario replays unless you pass --har-update.
answered by Reeta NandalSDODS team

Know the answer?

Wrap commands and output in triple backticks and they will render as a code block.

Checking whether you’re signed in…

Have a different question? Ask it.

Green on my machine, red on the runner — it was replaying a HAR the whole time

2 answers

Know the answer?

Related