When should I reach for the mock step instead of @har, or the other way round?

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.

Both stub the network. I can write this:

gherkin

When I mock "**/api/banner" with JSON:
  """json
  { "text": "Welcome {{username}}" }
  """

or I can tag the scenario @har:banner and record it. They look interchangeable from where I am standing. Is there a rule for which one to pick, or is it taste?

har mock ui

asked by Kostya Petrov

3 answers

Not taste. They answer different questions.
- The mock step is route fulfilment for one URL pattern with a payload you wrote. Use it when the payload is the point of the test: an empty list, a 500, a banner with a specific string in it. The response is authored, so it says exactly what you meant.
- @har:<name> is a snapshot of whatever the application actually sent, every request in the scenario, captured once and replayed verbatim. Use it when the payload is not the point and you just want the scenario to stop depending on a live service.
Rough test: if you would have to hand-write more than one or two responses to make the page render, record a HAR. If you are asserting on a value you chose, mock it inline, because a recording will drift away from your assertion the next time someone re-records it.
answered by Jide Okonkwo
We ended up using both in the same scenario and it works fine. Record the background traffic so the page loads offline, then mock the one endpoint whose shape the test is about. No trouble so far — the mock wins for its pattern and the recording answers everything else.
One thing to watch: tag the scenario @mock as well if it carries an inline mock, otherwise nobody grepping for stubbed scenarios will find it.
answered by Gio Castellano
One more axis nobody has mentioned: layers.
The mock step is a browser step. It fulfils a page route, so it does nothing for an @api scenario. The @har:<name> tag drives both layers from the same tag — the browser side through Playwright route interception, the API side through the API client’s own recorder and replayer.
So for an @api or @hybrid scenario that needs stubbed traffic, HAR is not one of two options, it is the option.
Network mocking and HAR
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.

When should I reach for the mock step instead of @har, or the other way round?

3 answers

Know the answer?

Related