docs and changelog update for nthCalledWith (jestjs#5734)

* docs and changelog update for nthCalledWith

* Update CHANGELOG.md

Author: Alaev

CHANGELOG.md

@@ -16,6 +16,8 @@
   ([#5670](https://github.com/facebook/jest/pull/5670))
 * `[expect]` Add inverse matchers (`expect.not.arrayContaining`, etc.,
   [#5517](https://github.com/facebook/jest/pull/5517))
+* `[expect]`Add nthCalledWith spy matcher
+  ([#5605](https://github.com/facebook/jest/pull/5605))
 * `[jest-cli]` Add `isSerial` property that runners can expose to specify that
   they can not run in parallel
   [#5706](https://github.com/facebook/jest/pull/5706)

docs/ExpectAPI.md

@@ -622,6 +622,25 @@ test('applying to all flavors does mango last', () => {
 });
 ```
 
+### `.nthCalledWith(nthCall, arg1, arg2, ....)`
+
+If you have a mock function, you can use `.nthCalledWith` to test what arguments
+it was nth called with. For example, let's say you have a
+`drinkEach(drink, Array<flavor>)` function that applies `f` to a bunch of
+flavors, and you want to ensure that when you call it, the first flavor it
+operates on is `'lemon'` and the second one is `'octopus'`. You can write:
+
+Note that, nth argument must be positive integer starting from 1.
+
+```js
+test('drinkEach drinks each drink', () => {
+  const drink = jest.fn();
+  drinkEach(drink, ['lemon', 'octopus']);
+  expect(drink).nthCalledWith(1, 'lemon');
+  expect(drink).nthCalledWith(2, 'octopus');
+});
+```
+
 ### `.toBeCloseTo(number, numDigits)`
 
 Using exact equality with floating point numbers is a bad idea. Rounding means