Why nock throw error `Nock: No match for request` when repeating request

Tests case:

nock('https://xxxx.com').get('/').times(1).reply(200, { mock: 1 });

// first times: print { mock: 1 }
// second and third times: throw error `Nock: No match for request`
for (let i = 0; i < 3; i++) {
  const {data} = await axios({
    url: 'https://xxxx.com/',
    method: 'GET',
  });
  console.log(data);
}

In README, means you can get real response from url you specified but not an error.

But in your tests cases: It should get error when repeating.

Version

• Nodejs: v12
• Nock: 13.0.7

[mastermatt]

Agreed, the docs need updating. PRs welcome!

@marcusNumminen to achieve your original, expected behavior the allowUnmocked flag needs to be passed when creating a Scope. https://github.com/nock/nock#allow-unmocked-requests-on-a-mocked-hostname

nock('https://xxxx.com', {allowUnmocked: true}).get('/').times(1).reply(200, { mock: 1 });

// first times: print { mock: 1 }
// second and third times attempt live calls over the network, assuming `nock.disableNetConnect()` wasn't called first
for (let i = 0; i < 3; i++) {
  const {data} = await axios({
    url: 'https://xxxx.com/',
    method: 'GET',
  });
  console.log(data);
}

[taozi0818]

Is this example https://github.com/nock/nock#repeat-response-n-times correct then? As I interpreted the example the fifth call should return the result from the “real” call to http://zombo.com/

No, you will get an error from the fifth call. See this tests case https://github.com/nock/nock/blob/main/tests/test_repeating.js README and the logic of code do not match.