Scenario tagged @har:products runs green but har/staging is still empty

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 added the tag and ran the suite. It passes, but nothing lands in projects/demo-shop/har/staging/.

gherkin

@ui @smoke @har:products
Scenario: Products render from recorded traffic
  Given I am on the inventory page
  Then I should see the text "Sauce Labs Backpack"

bash

bun run sdods run -p demo-shop -e staging -l ui -b chromium -t @smoke

The only odd thing in the output was a yellow line I scrolled past:

text

2021-10-21 09:12:44 [WARN] [har] @har:products has no recording at /work/projects/demo-shop/har/staging/products.har. Run: sdods har record -p demo-shop -e staging -t @har:products

Do I have to create the file by hand before the tag does anything?

har ui cli

asked by Lena Hartwig

2 answers

Accepted answer
The warning is the whole answer, and it even prints the command. A plain sdods run never records. The mode resolves like this: an explicit mode wins; otherwise it is replay when the file already exists, and off when it does not. Your file did not exist, so the hook fell to off and skipped routing entirely.
Record it once:
bash
```
bun run sdods har record -p demo-shop -e staging -t @har:products
```
That is the same thing as sdods run ... --har-update: requests go to the real network and the file is written on the way through. From then on every ordinary run of that scenario replays from har/staging/products.har, no flag needed.
You also get a sidecar next to it, products.har.json, holding the project, the env, the URL glob, the timestamp and the scenario titles that contributed.
answered by Jide Okonkwo
Adding one detail: if you leave -t off, har record runs the whole project in update mode and says so:
text
```
no --tags given: running the project in HAR update mode (only @har-tagged scenarios record)
```
Untagged scenarios just run normally, so it is safe, only slower. Prefer the tag expression when you know which recording you are refreshing.
Recording is authoring, not testing. Do it deliberately, look at the diff, commit it.
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.

Scenario tagged @har:products runs green but har/staging is still empty

2 answers

Know the answer?

Related