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.
I want the network traffic from a recording session so we can replay the flow offline in CI later. Do I record the flow, then do a second pass for the HAR, or is there a way to get both out of one sitting? Doing it twice means the two artefacts are of two slightly different journeys, which feels like it will bite us.
Accepted answer
One session. --save-har captures the network while you drive:
sdods record -p demo-shop -e staging --name checkout --user standard --save-har --har-glob "**/api/**"Three files come out of that:
projects/demo-shop/recorded/checkout.spec.ts
projects/demo-shop/har/staging/checkout.har
projects/demo-shop/har/staging/checkout.har.jsonThe .har.json is the sidecar: the URL glob you used, when it was captured, and source: codegen so you can tell it apart from a HAR produced by a run. --har-glob defaults to **/*, which on a real app means fonts, images and analytics beacons all land in the file, so narrowing it is usually right.
One naming detail: the name is slugified for both files. --name "Checkout Flow" gives you checkout-flow.spec.ts and checkout-flow.har, not what you typed, so pick something you would have typed anyway.
Capturing it is half the job — replay is keyed on the scenario tag, not on the recording. A scenario plays back from har/<env>/<name>.har because it carries @har:<name>, so when you convert the recording into a feature, tag the scenario to match the file you just wrote:
@ui @regression @har:checkout
Scenario: Standard user checks outThen:
sdods run -p demo-shop -e staging -t @har:checkout --har-replay --strict--strict aborts any request that is not in the HAR and blocks every other network call, which is what makes the CI run genuinely offline rather than mostly offline.
Two failure modes to know about. Lint tells you @har:checkout has no recorded file under har/<env>/checkout.har if the tag and the file drifted apart, which is the good outcome. And the tag has no room for spaces, so the slugified name from the recording is the one to type.
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.